Adam Jordens

Slightly delayed response but I would say that infrastructure-as-code (in the sense of codifying more than just a pipeline) has not been a significant pain point or blocker thus far.

This could be related to (a) the size of our cloud footprint and (b) how our approach to managing cloud resources has evolved since ~2009.

Nothing prevents storing pipeline configuration in git and syncing it to Spinnaker.

Foremast is a community provided solution that accomplishes much of this.

We’ve also added the ability to optionally lock a pipeline and prevent any modification from being made via the UI. In such scenarios the…

Somewhat architectural and environment-specific.

Rolling forward comes with the added assumption that your build/package tool chain is at least as reliable (if not more) as your Tier 1 services.

This might involve tools (Jenkins, Travis CI, Github, Stash, etc.) outside the control of a team that just…

Primarily, they are managed independently.

We have a configuration file in each repository (igor-nflx has igor.yml, orca-nflx has orca.yml, etc.)