Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[patch] Fix custom db2_namespace not being used in suite-db2-setup-manage #1366

Merged
merged 5 commits into from
Nov 22, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions tekton/src/pipelines/taskdefs/apps/db2-setup-manage.yml.j2
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,9 @@

- name: db2_instance_name
value: "mas-$(params.mas_instance_id)-$(params.mas_workspace_id)-manage"

- name: db2_namespace
value: "$(params.db2_namespace)"
# Only perform the hack if Manage is being installed, if we're using in-cluster system db and we're not using a dedicated Db2 instance for Manage (in-cluster or BYO)
when:
- input: "$(params.mas_app_channel_manage)"
Expand Down
3 changes: 3 additions & 0 deletions tekton/src/pipelines/taskdefs/apps/db2-setup-system.yml.j2
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,9 @@

- name: db2_instance_name
value: "mas-$(params.mas_instance_id)-system"

- name: db2_namespace
value: "$(params.db2_namespace)"
# Only perform the hack if Manage is being installed, if we're using in-cluster system db and we're not using a dedicated Db2 instance for Manage (in-cluster or BYO)
when:
- input: "$(params.mas_app_channel_manage)"
Expand Down
Loading