gitopsArchived
2 messages
Discuss continuous delivery of infrastructure
Archive: https://archive.sweetops.com/gitops/
RBover 5 years ago
Working with multiple pull requests in
.github/PULL_REQUEST_TEMPLATE/ with 2 files general.md and kms_secrets.md . When I create a new PR, I expected to see a button to select which template like we see with issue templates. What could the issue be ?
sheldonhover 5 years ago
Ok....
I want a cool win
Let's say I want to add a whitelisting entry to a security group in QA. Right now it's manual. Second option is terraform cloud cicd .... That said I am thinking of chatops or azure Pipelines or ssm automation runbook.
I want it to be super easy for team members to update their entry even if no GitHub knowledge so thinking maybe a messaging extension in teams to call an AWS lambda ? Easy to to do or learning curve steep. Also considered poshbot if I can do messaging extension but really wanted to use adaptive cards/form which makes sense to use lambda rest API for. Lastly I have mix of languages on the team and lambda would allow go, Powershell, and python contributions from team members vs poshbot probably making me run solo.
Messaging extension a good option or should I stick with GitHub runner and azure Pipelines concept, or gitops?
When I was talking through this with someone my preference would be pull request driven workflow. However I'm considering chat ops for this because a portion of those people don't even have experience with GitHub.
I want a cool win
Let's say I want to add a whitelisting entry to a security group in QA. Right now it's manual. Second option is terraform cloud cicd .... That said I am thinking of chatops or azure Pipelines or ssm automation runbook.
I want it to be super easy for team members to update their entry even if no GitHub knowledge so thinking maybe a messaging extension in teams to call an AWS lambda ? Easy to to do or learning curve steep. Also considered poshbot if I can do messaging extension but really wanted to use adaptive cards/form which makes sense to use lambda rest API for. Lastly I have mix of languages on the team and lambda would allow go, Powershell, and python contributions from team members vs poshbot probably making me run solo.
Messaging extension a good option or should I stick with GitHub runner and azure Pipelines concept, or gitops?
When I was talking through this with someone my preference would be pull request driven workflow. However I'm considering chat ops for this because a portion of those people don't even have experience with GitHub.