Here’s a look at the corresponding pipeline for the RBAC build that the pipeline engineering team owns.
As mentioned in rows 22 and 23, this pipeline also removes RBAC that is not present in the config file so that environments stay as clean as possible. We implemented this as a configuration as we wanted to implement the removal as a non-breaking change.
A fringe benefit of the Delivery Engineering team owning these pipelines is that we gain quite a bit of understanding and empathy when we use the same tools that our internal stakeholders also use. In addition, it gives us a venue to dogfood platform improvements such as build templates.
As mentioned on the preceding slide this pattern is representative of nearly
Let’s take a deeper look at one of the templates, in this case the template for how RBAC builds work. Templates provide a pretty easy way to roll out new features on the platform without those features being breaking changes for feature teams. As an example, we recently created a change service to bridge our Cloud Services world and our ITSM solution. After testing we can easily retrofit that interaction into existing practices.