Event banner
Event details
Is there a good reference or best practise recommendation on how to organize IaC code in repositories in regards to pure deployment code and configuration/parameter code (split?)
bmoore-msft
Microsoft
MicrosoftIDK know of a good reference or hard/fast rule. A few things to consider:
- never put secrets in source control - so if you have params that are secret, you need another store for those (github, azdo, keyvault)
- do you want [all] param/config changes to go through the same "test" that your deployment code does (e.g. do you want validate parameters in a pipeline or test) - and in some cases you may specifically *not* want this
- I see a mix of both in practice - some params are all on source control, others use pipeline/deploy time variables
Happy to expand more if you have more questions...