This message was deleted.
# puppets
Slackbot
06/22/2023, 4:24 PMThis message was deleted.
b
bastelfreak
06/22/2023, 5:10 PMYou could use tags during your puppet run to filter what gets applied
bastelfreak
06/22/2023, 5:10 PMbut I don't yet the see problem
bastelfreak
06/22/2023, 5:10 PMdo the Ruby devs and infra people work on the same branch/same environment?
bastelfreak
06/22/2023, 5:12 PMbecause when the devs are still developing their changes should not land in a branch that could/will be deployed to non-dev environments
k
kelvin
06/22/2023, 5:17 PMour codebase for infrastructure vs platform vs app dev is ultimatel merged to the same git branch, a “release” is created and deployed via Atlassian bamboo to each defined environment (nodes self-declare their environment name).
b
bastelfreak
06/22/2023, 5:18 PMmaybe that approach isn't the best 🙂
k
kelvin
06/22/2023, 5:18 PMall staff contributing to the puppet code base create a “feature” release branch, develop and test the code then merge to the main branch when completed, then create a new release.
b
bastelfreak
06/22/2023, 5:18 PMdo you have to merge stuff into it before it's production ready?
bastelfreak
06/22/2023, 5:19 PMso that means stuff is merged to main before it's ready?
k
kelvin
06/22/2023, 5:19 PMwell, what code is perfect when its merged to main? 😉
kelvin
06/22/2023, 5:20 PMbut yes, there are tests run in local VMs etc using the feature branch.
kelvin
06/22/2023, 5:22 PMUnit testing can only do so much. Ultimate proof is when a release is deployed to each lower environment, then validated in UAT, then pushed to Production.
b
bastelfreak
06/22/2023, 5:23 PMI would work with feature flags that you configure via hiera/an ENC and try to version the code from the different teams in own modules
k
kelvin
06/22/2023, 5:38 PMI’ll look into that.
b
bastelfreak
06/22/2023, 5:39 PMif you have any questions or need ideas, just ask
👍 1
2 Views