Do you care about the quality of your infra code?
A. As much as product code
B. Somewhat but mostly no
C. We create infra via UI
Let's discuss how do you manage Infra code! Feel free to share your thoughts in the comments section.
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (5)
Always infrastructure as code. So A
If DevOps/Infrastructure is not good enough then all the work you did on the product would not see its full potential. Having a reliable CI/CD pipeline which takes "just the right amount of time" is crucial in ensuring that you remain confident in your product code.
I initially started with UI based infra, but soon learned that infrastructure is not a separate thing, but part of the product, even if it is not shipped to the customer. Now I prefer YAML based infrastructure pipelines and proper reporting of tests, data and other assets.
Great points Manish. I wonder if the resistance is also because of lack of good guidelines for building infra as code.
Definitely A, but I'm in the DevOps consultancy team and we do a lot of infrastructure design. 😉
Makes sense. Any particular practices you follow for managing the infra as code?
We use Terraform and try to keep everything there. If that's not possible for some reason, we try to open issues so that it would be possible in the future and document the manual steps with a link to that issue.
Additionally, we heavily use Terraform modules, so that the "business logic" lies in the module and we only parametrize it in the different stage directories.