-
Notifications
You must be signed in to change notification settings - Fork 15
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
workflow to deploy to test environment #879
base: main
Are you sure you want to change the base?
Conversation
run: | | ||
echo $VAULT_PW > .vault_password | ||
bash ops/secrets --decrypt | ||
mv -fv shared_files/encrypted/* shared_files/decrypted/ |
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.
We might be able to switch out this secrets step to use AWS Parameter Store instead.
- name: Deploy to Test Environment | ||
run: | | ||
# Stop the existing containers if any | ||
docker-compose down |
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.
Should be in cleanup if needed (maybe not given short-lived self-hosted, or definitely not if on github hosted infra)
docker-compose down | ||
|
||
# Start the application in the test environment | ||
docker-compose up -d |
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.
TODO: deploy to test environment instead of running locally
@gsf @christopher-maboh Is this still relevant? I am unable to see the PLT ticket. |
@gsf @christopher-maboh bumping again to see if we still need this? |
🎫 Ticket
https://jira.cms.gov/browse/BCDA-PLT-187
🛠 Changes
(What was added, updated, or removed in this PR.)
Workflow to deploy to test environment added
ℹ️ Context for reviewers
(Background context, more in-depth details of the implementation, and anything else you'd like to call out or ask reviewers.)
Create a GitHub Actions workflow in the bcda-app repo to deploy application changes to the test environment on merge to the main branch.
✅ Acceptance Validation
(How were the changes verified? Did you fully test the acceptance criteria in the ticket? Provide reproducible testing instructions and screenshots if applicable.)
🔒 Security Implications
If any security implications apply, add Jason Ashbaugh (GitHub username: StewGoin) as a reviewer and do not merge this PR without his approval.