-
Notifications
You must be signed in to change notification settings - Fork 2
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
PLT-642 Adding verify scripts and deployment verification workflow #1402
Conversation
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.
Seems like a lot of duplication to have a separate verify script for each environment. Can it be parameterized?
I'm still seeing what looks like an error in the latest run: https://github.com/CMSgov/ab2d/actions/runs/12837809052/job/35803223841?pr=1402#step:6:76 |
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.
Looks good! I'd still like to see the output of those curl commands in the logs (via tee or something), and I'd prefer we pull BASIC_AUTH from the parameter store, but that can be changed later.
🎫 Ticket
https://jira.cms.gov/browse/PLT-642
ℹ️ Context
This is a new addition to our github actions workflows to verify our deployments
🧪 Validation
The test will be validated by github actions test runs.