-
Notifications
You must be signed in to change notification settings - Fork 9
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
have a way to test Terraform changes more safely #830
Comments
More support for this, from the official docs:
|
Have a question out to @cal-itp/cdt-devsecops about whether we need to use two Subscriptions, as that complicates the Pipeline. (From what I can tell, the service connection name is read at "compile time", which restricts what logic can be used to determine it.) Waiting on their answer before continuing, one way or another. |
Still ongoing as we propagate the changes up. |
The new dev and test app service instances are live and well. The custom domains (dev-benefits.calitp.org and test-benefits.calitp.org) are still pointing to the old slots via Front Door, now waiting on @cal-itp/cdt-devsecops to update those. Once that's done, we can deploy to production, which will delete the old slots etc. cc #1170 |
The new dev and test app service instances are live and well. Next, we'll deploy to production, which will delete the old slots etc. cc #1170 |
While we're still working on the cleanup of production, this task is technically done. |
Currently, our different environments are set up as App Service slots. This means infrastructure (a.k.a. Terraform) changes outside of slots apply to all of them, meaning there isn't an easy way to test those changes beyond a
plan
.I propose we use a dedicated Resource Group (maybe also a dedicated subscription?) to create a full
staging
environment, perhaps with some features like the Monitors disabled. We might want to go all the way and make one fordev
, and get rid of our use of slots. Open to feedback here.cc @cal-itp/cdt-devsecops
Acceptance Criteria
Additional context
This would have helped prevent the 7/21 downtime.
The text was updated successfully, but these errors were encountered: