Promoting and Deploying Configuration

After configuration changes pass review, the pipeline is ready to promote those changes into a pre-production and then production environments. Manual configuration access should not be available in pre-production or production environments, and this deployment should be automated in a similar or identical form of any other environment. Environments that are logically further in the promotion process beyond controlled testing environments (such as QA or user acceptance testing environments) should have continuous monitoring for errors as well as acceptable performance thresholds and alerting of outages. There should be an incident response plan for any anomalies that may be detected. Notification of anomalies could trigger an automated rollback if mutation outcomes can be guaranteed.

Forms of deployment of approved configuration include: