Skip to content

Allow specification of any schema name in MREF SaaS - #2583

Open
Sakshi-Singhroha1 wants to merge 1 commit into
masterfrom
mascore-10022
Open

Allow specification of any schema name in MREF SaaS#2583
Sakshi-Singhroha1 wants to merge 1 commit into
masterfrom
mascore-10022

Conversation

@Sakshi-Singhroha1

Copy link
Copy Markdown
Contributor

Issue
https://jsw.ibm.com/browse/MASCORE-10022
https://jsw.ibm.com/browse/MASCORE-15753
https://jsw.ibm.com/browse/MASCORE-17866

Description
Added support for configurable TRIRIGA schema name in the gitops-db2u-database CLI function. Previously the schema name was hardcoded as TRIDATA in all Facilities DB2 setup scripts. This change allows operators to specify a custom schema name via --facilities-db2-schema flag, defaulting to TRIDATA to ensure all existing deployments are completely unaffected.

Changes made:

functions/gitops_db2u_database — added --facilities-db2-schema CLI flag, FACILITIES_DB2_SCHEMA env var with default TRIDATA, and display in settings summary
ibm-db2u-database.yaml.j2 — added facilities_db2_schema to generated gitops-envs YAML for facilities instances only (conditionally written when MAS_APP_ID == 'facilities' and value is defined)

Test Results

  • Tested end-to-end on noble10/inst02:
  • facilities_db2_schema: MYSCHEMA flows correctly from mas-instance-params.yaml → pipeline → gitops-envs
  • Pipeline log confirmed: facilities-db2-schema: MYSCHEMA
  • Postsync job completed successfully with correct schema
  • image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants