-
Notifications
You must be signed in to change notification settings - Fork 31
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
Automate data load for feature branches #763
Conversation
95aa8e1
to
eeb0525
Compare
…complains about Sub if you use it redundantly
…riority for subdomain listener rule because it must be unique
db13daf
to
06ec648
Compare
I'm done with this for now, unless there are changes you'd like made @acdha The most recent test was a success |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are the changes for bastion 1/2 necessary now that there's a the dataloadhost declaration? I'm wondering whether we should just have that confined to that purpose, set InstanceInitiatedShutdownBehavior=terminate
, and add a shutdown -h now
call to the end of the user-data script.
I still use the bastion host template for loading DB dumps to dev / test / stage and get the DB dump from prod. It's not needed for loading data to feature branch deployments. But the changes I made there make it much simpler to dump or restore in the four main environments. I will add the shutdown stuff. |
I need to merge this one before we can use the feature branch deployment. I'm happy to make changes even after the stuff is merged. |
Refs #765