brightbox/terraform-provider-brightbox

Terraform Brightbox Cloud provider

terraform-provider-brightbox's Issues

Error: unprocessable_entity: policy is linked to a server group with active servers

Hello, while working on this PR: flatcar/flatcar-terraform#22 (providing Kubernetes bootstraping example on Brightbox using Flatcar OS) I faced the following issue while running terraform destroy:

brightbox_firewall_rule.kubernetes_api: Destroying... [id=fwr-dd3j0]
brightbox_firewall_rule.ssh: Destroying... [id=fwr-9adcl]
brightbox_firewall_rule.workers: Destroying... [id=fwr-vfx67]
brightbox_server.worker[0]: Destroying... [id=srv-bcse0]
brightbox_server.worker[2]: Destroying... [id=srv-yzqg2]
brightbox_server.worker[1]: Destroying... [id=srv-56o2m]
brightbox_firewall_rule.internet: Destroying... [id=fwr-49dka]
brightbox_firewall_rule.internet: Destruction complete after 0s
brightbox_firewall_rule.workers: Destruction complete after 0s
brightbox_firewall_rule.ssh: Destruction complete after 0s
brightbox_firewall_rule.kubernetes_api: Destruction complete after 1s
brightbox_firewall_policy.kubernetes: Destroying... [id=fwp-8d168]
brightbox_server.worker[1]: Still destroying... [id=srv-56o2m, 10s elapsed]
brightbox_server.worker[2]: Still destroying... [id=srv-yzqg2, 10s elapsed]
brightbox_server.worker[0]: Still destroying... [id=srv-bcse0, 10s elapsed]
brightbox_server.worker[1]: Destruction complete after 11s
brightbox_server.worker[0]: Destruction complete after 14s
brightbox_server.worker[2]: Destruction complete after 14s
brightbox_cloudip.control-plane: Destroying... [id=cip-5iirw]
brightbox_cloudip.control-plane: Destruction complete after 1s
brightbox_server.control-plane: Destroying... [id=srv-n4r1u]
brightbox_server.control-plane: Still destroying... [id=srv-n4r1u, 10s elapsed]
brightbox_server.control-plane: Destruction complete after 13s
╷
│ Error: unprocessable_entity: policy is linked to a server group with active servers
│
│
╵

and running the same command right after did the trick:

brightbox_firewall_policy.kubernetes: Destroying... [id=fwp-8d168]
brightbox_firewall_policy.kubernetes: Destruction complete after 0s
brightbox_server_group.kubernetes: Destroying... [id=grp-ws0ds]
brightbox_server_group.kubernetes: Destruction complete after 1s

Destroy complete! Resources: 2 destroyed.

Possible bug in v3: "Error: unprocessable_entity: This required parameter is missing: account_id"

I just upgraded the brightbox provider to v3.0.0 and attempted to import an existing firewall policy.

I got this error "Error: unprocessable_entity: This required parameter is missing: account_id"

Checked the terraform documentation for the brightbox_firewall_policy, and there is no mention of an account_id.

Downgraded the provider to v2.2.0, re-ran the import command. All works fine.

Package for darwin_arm64

I've just switched to a new Apple Silicon Macbook Pro and see the following when running terraform init:

Provider registry.terraform.io/brightbox/brightbox v2.0.6 does not have a package available for your current platform, darwin_arm64.

Are there any plans to provide a compatible package?

[PROPOSAL] Switch to Go Modules

As part of the preparation for Terraform v0.12, we would like to migrate all providers to use Go Modules. We plan to continue checking dependencies into vendor/ to remain compatible with existing tooling/CI for a period of time, however go modules will be used for management. Go Modules is the official solution for the go programming language, we understand some providers might not want this change yet, however we encourage providers to begin looking towards the switch as this is how we will be managing all Go projects in the future. Would maintainers please react with 👍 for support, or 👎 if you wish to have this provider omitted from the first wave of pull requests. If your provider is in support, we would ask that you avoid merging any pull requests that mutate the dependencies while the Go Modules PR is open (in fact a total codefreeze would be even more helpful), otherwise we will need to close that PR and re-run go mod init. Once merged, dependencies can be added or updated as follows:

$ GO111MODULE=on go get github.com/some/module@master
$ GO111MODULE=on go mod tidy
$ GO111MODULE=on go mod vendor

GO111MODULE=on might be unnecessary depending on your environment, this example will fetch a module @ master and record it in your project's go.mod and go.sum files. It's a good idea to tidy up afterward and then copy the dependencies into vendor/. To remove dependencies from your project, simply remove all usage from your codebase and run:

$ GO111MODULE=on go mody tidy
$ GO111MODULE=on go mod vendor

Thank you sincerely for all your time, contributions, and cooperation!

Orbit container created_at 'changes made outside of Terraform'

On each apply, an Orbit container's created_at attribute is updated to the current date/time.

Note: Objects have changed outside of Terraform

Terraform detected the following changes made outside of Terraform since the last "terraform apply":

  # brightbox_orbit_container.name has been changed
  ~ resource "brightbox_orbit_container" "name" {
      ~ created_at      = "2021-05-21T01:27:13Z" -> "2021-05-21T01:28:25Z"
        id              = "name"
        name            = "name"
        # (6 unchanged attributes hidden)
    }

Unless you have made equivalent changes to your configuration, or ignored the relevant attributes 
using ignore_changes, the following plan may include actions to undo or respond to these changes.

Terraform v0.15.4, Brightbox provider v2.0.4.

(No rush on this as far as I'm concerned; not in active use here.)