-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve readme with details on how to access terraform state #1090
Comments
That readme was written a while ago and I think the level of detail of which pulsar cluster is in which tenancy now belongs in https://github.com/usegalaxy-au/operations (it is missing from here too) |
@nuwang do you have access to this repo? |
I guess we should at least mention the state file, and where to find the operations repo then. The instructions that are currently in this readme won't work and are therefore of limited use. We could remove it altogether perhaps in favour of adding everything to operations. And I'm assuming the access issue is sorted now. |
Actually the way that the state files are set up there is no extra step in those instructions. It is declared in a file called backends.tf in each terraform folder |
Ok. That solves most of my concerns except C. Is that automatically handled? The overall idea is still worth a mention in ops/readme I suppose. |
For mac users there is an extra complication in using swift backends: 'swift' means something else to a mac and has to be overridden. I'll see if I can find how that was done, it was a while ago. As for the other concern, I have not seen anything go wrong - the first thing terraform says when running "terraform plan" or "terraform apply" is "Acquiring state lockfile". It will be important to document which thing belongs to which tenancy and make sure that you, me and JL have access to all of them. |
Sounds good. How are the swift credentials provided? |
openstack rc file |
The readme is missing information on how to access shared terraform state:
https://github.com/usegalaxy-au/infrastructure/blob/e70e28f268511ac96f24e893d80385f0b73454b0/README.md#operationrunning-the-playbooks
The following details would be used
a. Which bucket the terraform state is stored in
b. How to make sure that state is used when performing a terraform plan/apply on the commandline.
c. Any other concerns regarding locking and simultaneous application when using the state.
The text was updated successfully, but these errors were encountered: