[swift] Terraform has deprecated the Swift backend
Hey,
It has come to our attention that Terraform has recently added deprecation messages to a number of backends, including Swift[0], warning that these backends will be removed in a future version of Terraform. Unfortunately we don't have the bandwidth within Catalyst Cloud to pick this up, but I was hopeful that there'd be others on this list who share our concern.
It looks as though Terraform has had the Swift backend marked as unmaintained since at least March 2020[1].
If there is another backend, or another method of managing Swift that isn't the S3 API then I'd be keen to hear about it.
Kind regards, Andrew
[0] https://github.com/hashicorp/terraform/commit/7941b2fbdc33a42a68b9b32af51e09... [1] https://github.com/hashicorp/terraform/commit/c434db158e631b0bfddb92e1dd342b...
Do you use the swift backend for terraform state storage? It looks like they're dumping a bunch of other backends too - maybe they did a user-survey and they're just keeping the top-5 cloud providers or something.
On Thu, Aug 18, 2022 at 4:24 PM Andrew Ruthven andrew@etc.gen.nz wrote:
Hey,
It has come to our attention that Terraform has recently added deprecation messages to a number of backends, including Swift[0], warning that these backends will be removed in a future version of Terraform. Unfortunately we don't have the bandwidth within Catalyst Cloud to pick this up, but I was hopeful that there'd be others on this list who share our concern.
It looks as though Terraform has had the Swift backend marked as unmaintained since at least March 2020[1].
If there is another backend, or another method of managing Swift that isn't the S3 API then I'd be keen to hear about it.
Kind regards, Andrew
[0] https://github.com/hashicorp/terraform/commit/7941b2fbdc33a42a68b9b32af51e09... [1] https://github.com/hashicorp/terraform/commit/c434db158e631b0bfddb92e1dd342b...
--
Andrew Ruthven, Wellington, New Zealandandrew@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
S3 will do it.
On Fri, Aug 19, 2022 at 9:21 AM Clay Gerrard clay.gerrard@gmail.com wrote:
Do you use the swift backend for terraform state storage? It looks like they're dumping a bunch of other backends too - maybe they did a user-survey and they're just keeping the top-5 cloud providers or something.
On Thu, Aug 18, 2022 at 4:24 PM Andrew Ruthven andrew@etc.gen.nz wrote:
Hey,
It has come to our attention that Terraform has recently added deprecation messages to a number of backends, including Swift[0], warning that these backends will be removed in a future version of Terraform. Unfortunately we don't have the bandwidth within Catalyst Cloud to pick this up, but I was hopeful that there'd be others on this list who share our concern.
It looks as though Terraform has had the Swift backend marked as unmaintained since at least March 2020[1].
If there is another backend, or another method of managing Swift that isn't the S3 API then I'd be keen to hear about it.
Kind regards, Andrew
[0] https://github.com/hashicorp/terraform/commit/7941b2fbdc33a42a68b9b32af51e09... [1] https://github.com/hashicorp/terraform/commit/c434db158e631b0bfddb92e1dd342b...
--
Andrew Ruthven, Wellington, New Zealandandrew@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
-- Clay Gerrard 210 788 9431
Hey,
Some of our customer are using the swift backend for terraform state storage. By the look of things they're going to drop all of the backends that are unmaintained.
We've had a look at the S3 remote, sadly it isn't suitable as it uses DynamoDB for locking. We'd rather not tell customers they have to use services from another cloud provider. :)
The locking in the Swift backend isn't that great either, as it appears to store the lock state in Swift which with eventual consistency...
It seems that our current recommendation to customers will end up being to use the PostgreSQL backend which they can use by deploying a Trove instance.
Cheers, Andrew
On Fri, 2022-08-19 at 10:49 -0500, Alvaro Soto wrote:
S3 will do it.
On Fri, Aug 19, 2022 at 9:21 AM Clay Gerrard clay.gerrard@gmail.com wrote:
Do you use the swift backend for terraform state storage? It looks like they're dumping a bunch of other backends too - maybe they did a user-survey and they're just keeping the top-5 cloud providers or something.
On Thu, Aug 18, 2022 at 4:24 PM Andrew Ruthven andrew@etc.gen.nz wrote:
Hey,
It has come to our attention that Terraform has recently added deprecation messages to a number of backends, including Swift[0], warning that these backends will be removed in a future version of Terraform. Unfortunately we don't have the bandwidth within Catalyst Cloud to pick this up, but I was hopeful that there'd be others on this list who share our concern.
It looks as though Terraform has had the Swift backend marked as unmaintained since at least March 2020[1].
If there is another backend, or another method of managing Swift that isn't the S3 API then I'd be keen to hear about it.
Kind regards, Andrew
[0] https://github.com/hashicorp/terraform/commit/7941b2fbdc33a42a68b9b32af51e09... [1] https://github.com/hashicorp/terraform/commit/c434db158e631b0bfddb92e1dd342b...
-- Andrew Ruthven, Wellington, New Zealand andrew@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
-- Clay Gerrard 210 788 9431
Hello,
This is a rather sad trend that we are seeing now, unfortunately that’s the reality when people don’t step up supporting the integrations they need in open source.
We are seeing the same issue in Ceph RadosGW now that there is interest in deprecating the whole Barbican integration which I assume we are not alone in using.
I for one will we be working on supporting the Ceph developers maintaining the Barbican support hopefully somebody with insight into Terraform can do the same and step up to maintain the Swift support.
Best regards Tobias
Sent from my iPhone
On 20 Aug 2022, at 06:44, Andrew Ruthven andrew@etc.gen.nz wrote:
Hey,
Some of our customer are using the swift backend for terraform state storage. By the look of things they're going to drop all of the backends that are unmaintained.
We've had a look at the S3 remote, sadly it isn't suitable as it uses DynamoDB for locking. We'd rather not tell customers they have to use services from another cloud provider. :)
The locking in the Swift backend isn't that great either, as it appears to store the lock state in Swift which with eventual consistency...
It seems that our current recommendation to customers will end up being to use the PostgreSQL backend which they can use by deploying a Trove instance.
Cheers, Andrew
On Fri, 2022-08-19 at 10:49 -0500, Alvaro Soto wrote: S3 will do it.
On Fri, Aug 19, 2022 at 9:21 AM Clay Gerrard <clay.gerrard@gmail.commailto:clay.gerrard@gmail.com> wrote: Do you use the swift backend for terraform state storage? It looks like they're dumping a bunch of other backends too - maybe they did a user-survey and they're just keeping the top-5 cloud providers or something.
On Thu, Aug 18, 2022 at 4:24 PM Andrew Ruthven <andrew@etc.gen.nzmailto:andrew@etc.gen.nz> wrote: Hey,
It has come to our attention that Terraform has recently added deprecation messages to a number of backends, including Swift[0], warning that these backends will be removed in a future version of Terraform. Unfortunately we don't have the bandwidth within Catalyst Cloud to pick this up, but I was hopeful that there'd be others on this list who share our concern.
It looks as though Terraform has had the Swift backend marked as unmaintained since at least March 2020[1].
If there is another backend, or another method of managing Swift that isn't the S3 API then I'd be keen to hear about it.
Kind regards, Andrew
[0] https://github.com/hashicorp/terraform/commit/7941b2fbdc33a42a68b9b32af51e09... [1] https://github.com/hashicorp/terraform/commit/c434db158e631b0bfddb92e1dd342b...
--
Andrew Ruthven, Wellington, New Zealand andrew@etc.gen.nzmailto:andrew@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
-- Clay Gerrard 210 788 9431
--
Andrew Ruthven, Wellington, New Zealand andrew@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
participants (4)
-
Alvaro Soto
-
Andrew Ruthven
-
Clay Gerrard
-
Tobias Urdin