Over the course of this book, we have been focused on a unidirectional process of pushing software out to given environments (including production). This in essence revolves around a software-engineering team having confidence in their changes, and therefore triggering the process to ship it or an Ops team who are confident to ship a config as code change.
What if you were to turn this around and allow the users of your software platform to initiate the pulling of your software at will? It might sound strange, but there are a few legitimate scenarios in which this could be required.
Let's look at a few scenarios:
- You have an implementation team that supports the on-boarding of new customers, and they would like to test out different scenarios and use cases so that they can ensure their manual test scripts, FAQs, and training documentation are up to...