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

Use case for multiple environments (DEV, QA/UAT/, PROD)? #170

Open
nmajin opened this issue Mar 15, 2022 · 0 comments
Open

Use case for multiple environments (DEV, QA/UAT/, PROD)? #170

nmajin opened this issue Mar 15, 2022 · 0 comments

Comments

@nmajin
Copy link

nmajin commented Mar 15, 2022

I am just curious if this is accounting for the GitOps dilemma of multiple environments; pushing changes to DEV clusters and checking things out then triggering a push to QA clusters, etc.

Everything I've read goes against multiple branches and there are many cons with any option I've looked at (multiple branches, multiple repos).

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

No branches or pull requests

1 participant