-
Notifications
You must be signed in to change notification settings - Fork 0
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
[CHORE] Fix Dev #480
Comments
Created a PR to include additional deletes and cleanups for the dev environment when cloudwatch is enabled. Have to wait till after this morning's release to merge it. |
Updates merged. Will see how this runs at the end of the week. |
@P0NDER0SA to "QA" nothing |
Didn't deploy again this morning due to existing resources... I just reran the delete script and will try launching again. I'm not sure what's going on :| |
update: Ben knows what's going on! New Relic. Always New Relic. |
Bunch of problems with new relic, ses identities not being recreated, and cbs sensor bucket name being stolen. All fixed, moving to QA |
infra dev is fine 🎉 |
Dev workflows (Delete and Recreate) did run, but there were two failures in the recreate for system status and sms to sqs callbacks. Ben has work being done to migrate this workflow to use helmfile for dev like it does on Staging -- but it's still in progress since the code freeze and hasn't been applied yet. |
let's checjk the health on this again next Monday |
We let the automation runs to see if that works but there was a new change that prevented DEV from working properly. |
Dev is up and running |
Had a problem with AWS timeouts. I've increased it to 4hrs on dv |
Now we have a problem where AWS can't log in :| Debugging and trying a different role |
Dev fixed - moved to the correct role. |
What
Dev is messed up because of the cloudwatch stuff. Need to add this to the delete scripts.
Why
Dev is important! BCP!
Acceptance Criteria
Resources
Triggers / Schedule
Describe the schedule or trigger for this chore. When should it be done?
The text was updated successfully, but these errors were encountered: