Closed avoidik closed 1 year ago
This has been working for us for a while already:
terraform {
backend "swift" {
cloud = "project-name"
container = "terraform-state"
archive_container = "terraform-state-archive"
state_name = "project-name.tfstate.tf"
}
}
provider "openstack" {
cloud = "project-name"
}
Considering that the swift backend is deprecated and from my testing broken in newer terraform releases, I leverage the S3 compatibility of swift instead.
Hello! Thanks for reporting this.
We removed the Swift backend in Terraform v1.3 because it hasn't had a dedicated maintainer for a few versions now and so it was becoming problematic to keep working in newer Terraform versions. Since that backend is no longer present in the Terraform codebase, I'm going to close this issue.
If you're currently using this backend with an older version of Terraform, see Removal of Deprecated State Storage Backends in the Terraform v1.3 upgrade guide for some information on the available options for migration.
Thanks again!
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
OpenStack provider already supports clouds.yaml as the configuration source. It would be great if the same mechanics will be adopted to Swift state storage backend.
https://github.com/terraform-providers/terraform-provider-openstack/pull/154 https://github.com/terraform-providers/terraform-provider-openstack/issues/122