Marques Johansson

https://peps.python.org/pep-0423/#overview has a section on namespacing ([Top-level namespace](https://peps.python.org/pep-0423/#top-level-namespace-relates-to-code-ownership)). Perhaps `equinix-labs/equinix.metal` or `github.com/equinix-labs/python-equinix` and pypi `equinix` (`from equinix import metal`)? https://peps.python.org/pep-0423/#how-to-rename-a-project

> Consider whether we should call it “maintained”. Maybe some kind of EOL status or deprecated tag. https://github.com/packethost/standards/issues/77

> _if we do go that route_, we should introduce a new package for that purpose and hide both the SDK and framework providers behind it. Cyclical dependencies have been...

I'm marques.packet in the Equinix Metal Comunity Slack, @jbg. Was this a reserved hardware instance? Could you provide any details from the device timeline if it is still available? I...

Another possibility, was the resource locked?

> Does the provider handle HTTP errors correctly? Maybe there was a brief API outage when it tried to delete the server. Errors like a 403 and 404 are treated...

Coming from 3.5.0, I'm not sure that 3.6.0->3.6.1 fix would be a factor. This EM API 500 error line (in the working state, after manually updating the peers) is suspicious....

https://github.com/equinix/cloud-provider-equinix-metal/issues/198#issuecomment-1116002323 could be related too ("Other than at startup,...")

This is still a problem: ``` $ terraform version Terraform v1.7.1 on linux_arm64 + provider registry.terraform.io/equinix/equinix v1.26.0 ``` The stack traces from this bug are somewhat arbitrary.

@mristok api.equinix.com should be used, it is used in other integrations including ClusterAPI, Terraform, MetalCLI and the new Ansible Equinix collection. In the Ansible Equinix collection we are using https://github.com/equinix-labs/metal-python/...