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.

Sign up for GitHub

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

[fix]: [CDS-105909]: Add multi service runtime inputs not supported limitation #9110

Merged
merged 1 commit into from
Jan 22, 2025
Merged

[fix]: [CDS-105909]: Add multi service runtime inputs not supported limitation #9110

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
1 change: 1 addition & 0 deletions docs/continuous-delivery/x-platform-cd-features/advanced/multiserv-multienv.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -489,5 +489,6 @@ By default, Harness uses numerical indices for the matrix naming strategy. Enabl
* Reconciliation for Harness services, environments, and infrastructure definitions is not supported for deployments using multiple services, environments, or infrastructures, respectively.
* You cannot propagate multi environments between stages
* When using stage variables with multi environments, the expression used for a particular stage changes. For example, if the expression for a stage without multi environment is `<+pipeline.stages.sampleStage.variables.resourceNamePrefix>`, for multi environment, expression path changes and gets updated based on the iteration number of stage like this, `<+pipeline.stages.sampleStage_1.variables.resourceNamePrefix>`.
* Runtime inputs for service overrides are not supported when using multi-service configuration.


Loading