Promotable Environments (Eng)

[dotCMS-Machine-User]

Infrastructure and Config promotion

1. A *NO-OP *change goes through the pipeline and into an environment without downtime
2. 1. Who’s it for
   2. 1. As a dotCMS developer, I can be confident that my local, sandbox, qa, and production environments are consistent, so that I can separate concerns and interact with upgrade and running behaviour. 
      2. As a dotCMS customer, I want to apply a config change without downtime
   3. What does it do
   4. 1. Allow a developer to interact with upgrades/deployments
      2. Test and interact with the init container
      3. Test that a no-op change is indeed zero downtime
      4. reproducibility between local and sandbox environments (via Helm charts)
      5. 1. Infra config
         2. Envvars
         3. …etc  
      6. A config change should allow for restart without downtime.
   5. What does it NOT do
   6. 1. DB and API changes would work (via init container) but with downtime
      2. It does not guarantee that something is broken beyond dotCMS server starting up 
      3. Allow for anything other than starter starter as dotCMS 
      4. Solve the need to manually update the image name/version in the values file to rollout a new version. 
   7. What is required for this to be available 
   8. 1. Tomcat redis sessions
      2. Current -> current
   9. What sprint size things do we need to do to get there and that we can demo?
   10. 1. Tomcat redis sessions for sandboxes
       2. dotCMS image becomes the init container 
       3. Connect helm-chart into the sandbox (sandboxes get additional functionality via helm-charts and values.yaml file)
       4. 1. Replace scripts in sandbox tooling with helm-charts
          2. Versioning for helm charts
       5. Clean up the logs with probe where it throws exception each time it’s hit
       6. Helm charts for dotCMS cloud customers on current

Important

The end result here is that the 8 customers on current are running using the same helm charts we're using locally and in sandbox