Skip to main content

Update chart.yml and Release to Lower env

At the time of cutting the New Release

-The enterprise chart should be behind the release version: Release-1.30---chart:1.29.0

-Update the changelog EX:## 1.29.0

  • As per our new approach to maintain a consistent deployment process, The chart version should be behind the current release version of 1.29.0.

-Same time the development envs should be updated , these versions should be one version ahead the current Enterprise chart version. (ex:1.29.0 Meso and Neo)

Deployment process for the Lower env Julius, Nero

These branches should be upto date before we cut from IN branch

Repos to be cut (if any additional Repos, check with the development team)

Empower : Make a image from CI Terraform (2 images come ADF and Databricks)

Empower ui : ui Front end CI

Empower-core-api-service : coreapi- Image Empower core API CI

Empower-Data-Api-Service : empower Data Api CI

Empower-spark : Spark WF- Push Empowerspark Library

Empower-front-door : empower-service (FDS to be cut done from development (check with Thomas))

Empower-terraform : Terraform- Terraform ci publish oci image

empower-client-config-generator : "Merge to IN" CI, then merge IN into releases/vX.XX branch. See Documentation: Releases. Should follow empower-terraform releases closely.

If the images are not created automatically

please go to each repo : Actions: Click on the appropriate workflow and select IN branch and Run workflow.

The images are created here : under package : https://github.com/orgs/empowerplatform/packages

The images will propagate to Nero and Julius envs as there is a image policy automation set-up.

Make sure when the deployment is completed.

Log in to each client tenant ADF and Databricks.

Check for the updated version of empower spark, Jobpolicy ID, Poolids L and M are matching with the ADF Global Parameters.

Check the CoreAPibaseurl : Current Version Ex: https://synqor.empoweranalytics.io/core/pd/api/docs/

Check StateDbRestApiBaseUrl : Current Version EX: https://synqor.empoweranalytics.io/data/pd/docs

https://meso.empoweranalytics.io/data-sources(fullscreen:settings/about)

Once all the version are good.

Declare a Code freeze.

Once the Release planning meeting is completed, we will come to know the date for the code freeze.

Release Process for Global Charts

Scope: charts/empower-global

Out of Scope: Other charts (Use process described above)

Context: This version process, being global, has a wider scope than current releases, so trying to follow existing release versioning for the charts will cause confusion, which is the opposite of what we want, for a critical/global chart.

Solution:

-Immediately: the next major changes to the chart should be 2.0.0, to indicate a major change (Refactoring the Dev SSO) and to signify that we've changed versioning for the Empower Chart. Additionally: add this Wiki page/section into the Readme.md file.

-Patch Changes: Update the changelog for documentation or display content (or as a way to trigger a release). EX:## 2.0.1 This version should not be tied to release version in any way.

  • Changing a word in a comment/documentation
  • A situation that requires re-deploying an existing release

-Minor Changes: Update the changelog for minor changes that are not breaking changes or adding/changing significant functionality EX:## 2.1.0 This version should not be tied to release version in any way.

  • Changing a default value on an existing property.

-Major Changes: Update the changelog for major changes that are breaking changes or adding significant functionality EX:## 3.0.0 This version should not be tied to release version in any way.

  • Migration of existing resources.
  • Removing or creation of entirely new App registration/resources.
  • Changing the name/definition/type of a property.
  • Adding a flag to enable existing property/functionality.

For safety and criticality, all changes, whether Major or Minor, should be tested with the "approveplan: manual" set on it, and the plan reviewed with at least two engineers before applying. There is room for much damage to be done with this chart and due dilligence needs to be done to protect against unintentional changes.