Pause all the pipeline from the Data Platform UI before proceeding to upgrade
-
Clone the transflux repository
git clone -b 5.1_f-Candidate https://efcx:RecRpsuH34yqp56YRFUb@gitlab.expertflow.com/cim/transflux.git $HOME/CX-5.1/transflux
-
Replace the existing configs with new ones as per following
-
transflux/dbt_schema/agent_state_summary_gold.ymlwithCX-5.1/transflux/dbt_schema/agent_state_summary_gold.yml -
transflux/config/bulk_upload_config_template.yamlwithCX-5.1/transflux/config/bulk_upload_config_template.yaml -
transflux/config/gold_15_minutes_queries_config_template.yamlwithCX-5.1/transflux/config/gold_15_minutes_queries_config_template.yaml -
transflux/config/data_migration_config.yamlwithCX-5.1/transflux/config/data_migration_config.yaml
-
-
Edit the existing
transflux/config/tenants.yaml
|
Before |
After (For MYSQL) |
After (For MSSQL) |
|---|---|---|
|
|
|
-
Delete the existing config maps and re-create them from
transfluxdirectory
# Delete existing config maps
k delete cm ef-transflux-config-cm -n expertflow
k delete cm ef-transflux-dbt-schema-cm -n expertflow
# Re-create the config maps
kubectl -n expertflow create configmap ef-transflux-config-cm --from-file=config
kubectl -n expertflow create configmap ef-transflux-dbt-schema-cm --from-file=dbt_schema
-
Edit the file
helm-values/cx-transflux-custom-values.yamlin thetransfluxdirectoryimage: repository: cim/cx-data-platform/build tag: 5-1-f-candidatebranch-d69c4689131e8129201984f15f943f4f2d434c50 -
Redeploy the solution
helm upgrade --install --namespace expertflow --set global.efCxReleaseName="ef-cx" cx-transflux --debug --values helm-values/cx-transflux-custom-values.yaml expertflow/transflux --version 5.1.0-rc.1
-
Once the pod is up, perform Alembic Schema Migrations using the guide https://expertflow-docs.atlassian.net/wiki/x/jADsRQ and use CX 5.1 version upgrade id available in attached document
-
Once done, please go to Data Platform UI and trigger the
Tenant-updates_5.1named dag and ensure from logs it passes successfully with no errors.