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.

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

[Feat]: Terraform and CircleCI to setup QA environments for each feature branch #342

Open
goseinthemachine opened this issue May 5, 2022 · 1 comment
Labels

Comments

@goseinthemachine
Copy link

Is your feature request related to a problem? Please describe.

The move to having QA being a part of the pod and being involved in each sprint requires more infrastructure. Had to setup a specific QA environment and figure out a process for having QA test on an automated deploy. Unfortunately the process I came up with right now currently requires a PR to be merged into the development branch before deploying to a QA environment.

Describe the solution you'd like.

Since each pod will eventually have its own QA members within the pod and there is a push to move to agile development where QA is a part of each issue moving forward to completion, I think there is a needto have multiple environments spun up on the fly for each PR going into QA review. That way each PR could be tested in isolation by the QA team members.

This deployment feature is similar to what I've seen Heroku and Render provide.

Describe alternatives you've considered

Heroku and Render appear to have this feature.

Heroku is currently having some issues though.

Additional context

I looked into this for a little bit and it doesn't seem like an easy task with our current infrastructure setup

  • AWS limitation may prevent this. Ran into issues with RDS instances limits.
  • Terraform cloud may be necessary to handle deployment secrets.
@michaelachrisco
Copy link
Contributor

michaelachrisco commented Oct 12, 2022

@goseinthemachine What issues is Heroku having? Sounds super interesting!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants