User Review( votes)
Azure pros share thoughts on the Don’t Repeat Yourself principle, app availability with Kubernetes Service, and Azure Policy processes.
The Don’t Repeat Yourself principle in DevOps Pipelines
Thomas Thornton noted the importance of the “DRY” (Don’t Repeat Yourself) principle when working with DevOps Pipelines. Essentially, what the phrase means is that users should avoid copying and pasting within pipelines and even avoid duplication generally. Users may want to parameterize, rely on variables, manage stages and tasks with fewer lines, plan for structure and refine logic.
Generally speaking, this may mean that the best approach involves less code and that users should plan to keep code unique. He wrote:
Create a set of pipeline templates that you can reuse and refactor to create further pipelines, I do this quite often and a lot of my work is done from a set of template(s) that I created previously and use and refactor to make the pipeline(s) more specific to the current requirements and environments that I am working on. Try to plan your pipeline before you begin writing it, think of it like a blog post – you want it to flow, why not follow that with your pipeline?
Users should set context and try to understand what it will achieve and apply the DRY principle as much as possible. Thornton added that users can also ask themselves whether the config has been repeated and whether there are ways to simplify or refactor it.
Boosting app availability with Kubernetes Service
FREE Membership Required to View Full Content:
Learn more about us here