Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Make PR based deploys to AWS #4

Open
mishraomp opened this issue Dec 11, 2024 · 1 comment
Open

Make PR based deploys to AWS #4

mishraomp opened this issue Dec 11, 2024 · 1 comment
Assignees
@DerekRoberts @mishraomp

Comments

@mishraomp
Copy link
Collaborator

Currently it is deploying to dev on merge
Ideally there would be no dev, it would be PR to TEST
each PR will have its own environment.
challenge would be to see how to play nicely with RDS.
@DerekRoberts DerekRoberts moved this from New to Sprint in DevOps (NR) Dec 11, 2024
@mishraomp
Copy link
Collaborator Author

mishraomp commented Dec 12, 2024 •
edited
Loading

idea,
fire a lambda function in pr open to create a new database in aurora instance for the pr deployment to use, the lambda function execution will be a need for the api to deploy.
fire a lambda function in pr close to drop the database in aurora for the pr

add pr env destroy to remove ecs cluster and cloudfront distribution when pr is closed or merged

similar pattern to what we have in QSOS with crunchy, each PR gets a database within same crunchy instance.

@DerekRoberts

fyi @marcellmueller

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DerekRoberts DerekRoberts

@mishraomp mishraomp

Labels
None yet
Projects
DevOps (NR)
Status: Sprint
Milestone
No milestone
Development

No branches or pull requests
2 participants
@DerekRoberts @mishraomp