Rework devcamcar's OpenStack Swift remote for new style state/remote. #2254
Conversation
Rework devcamcar's OpenStack Swift remote [pull request](#942) to work with Terraform's new `state/remote` and Gophercloud's current implementation. `Get()` changed up a bit from devcamcar's version (using different Gopercloud functionality resulted in less fussing around to figure out the error case). Otherwise this is a transliteration/remix of his ideas.
Rework devcamcar's OpenStack Swift remote [pull request](#942) to work with Terraform's new `state/remote` and Gophercloud's current implementation. `Get()` changed up a bit from devcamcar's version (using different Gopercloud functionality resulted in less fussing around to figure out the error case). Otherwise this is a transliteration/remix of his ideas.
Only run the Swift remote tests when OpenStack seems to have been set up and when the autho host is reachable.
…into swift-remote
|
ps. I wonder if there are places in the documentation that I should have mentioned this change? |
|
This LGTM. Great job. I'll update the website sources. |
Rework devcamcar's OpenStack Swift remote for new style state/remote.
|
I've been trying to use the thing that I've helped create, and I'm confused. The purpose of the remote storage of state is to avoid having to keep the state file consistent amongst multiple copies of the configuration directory (e.g. multiple users or work vs. home machines or...). Before remote storage existed, the state file could be kept consistent by committing it to source code control. Now it seems that we have to keep track of the fact that a system is using a particular remote state configuration by keeping the .terraform/terraform.state file in source control. We've traded an obvious file for a non-obvious file. It seems like it would make more sense to specify the remote state configuration in the config file with the rest of the system definition? [Is there a thread where this was discussed? I feel as if there's a mailing list or a chat room or .... that I should be following]. |
|
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. |
ghost
locked and limited conversation to collaborators
@devcamcar had a pull request that added a useful feature but used the old style remote interface.
I've remixed it to work with the state/remote interface. Get() changed up a bit to work with the current Gophercloud API's, but otherwise it's a straight transmogrification of his work.
It works with our Nebula (RIP) OpenStack cloud.