IaC in same repo as application code? I have been searching for examples and best practices on IaC for larger teams. Today I'm in the infrastructure team that manages all terraform in the company, but we discussed about moving that into each application repo. That gives us the advantage of knowing exactly the infra that was deployed with each app version, and gives the app team responsibility over the resources for each app, leaving us the job of maintaining the reusable modules, and reviewing their IaC changes before applying. But I haven't seen if this is a good/common practice, and if the tiny changes to the infra (say, changing an environment variable value or ASG desired count) triggering a whole application build/deploy would be good. Thoughts? |
No comments yet