Requesting Recommendations - Git Strategy for AWS Infrastructure with Terraform #169234
Replies: 2 comments
-
|
Option 1: Separate Branches for Each Environment (dev, qa, stg, prod) The second approach with feature branches merging into a dev branch and then into a prod branch is a better starting point. However, to make it effective for multiple environments, you'll need to use: |
Beta Was this translation helpful? Give feedback.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Why are you starting this discussion?
Question
What GitHub Actions topic or product is this about?
Misc
Discussion Details
I’m working on a requirement to deploy AWS EKS along with other AWS infrastructure components using Terraform. The code has been developed, and I’m planning to implement CI/CD using GitHub Actions.
We have four environments: Dev, QA, Staging (STG), and Production.
I’d like your expert opinion on the best branching strategy for managing these environments. Specifically:
Your guidance and recommendations would be greatly appreciated.
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions