pipelines/types: add monitorV2ScopeBindingFile to GenevaHealthStep#202
Merged
rachelvweber merged 1 commit intoAzure:mainfrom Feb 25, 2026
Merged
Conversation
shubhadapaithankar
force-pushed
the
add-scope-binding-support
branch
2 times, most recently
from
071058d to
b5eb0d2
Compare
Adds optional monitorV2ScopeBindingFile field to GenevaHealthStep to support multi-cloud monitor deployment via Geneva scope bindings. This enables a single shared set of monitors across Public and Fairfax by replacing cloud-specific values (e.g. account names) at deploy time.
shubhadapaithankar
force-pushed
the
add-scope-binding-support
branch
from
b5eb0d2 to
94ead08
Compare
rachelvweber
approved these changes
Feb 25, 2026
shubhadapaithankar
added a commit
to shubhadapaithankar/ARO-HCP
that referenced
this pull request
Feb 25, 2026
Picks up monitorV2ScopeBindingFile support in GenevaHealthStep (Azure/ARO-Tools#202) for multi-cloud Geneva monitor deployment.
shubhadapaithankar
added a commit
to shubhadapaithankar/ARO-HCP
that referenced
this pull request
Feb 25, 2026
Picks up monitorV2ScopeBindingFile support in GenevaHealthStep (Azure/ARO-Tools#202) for multi-cloud Geneva monitor deployment.
shubhadapaithankar
added a commit
to shubhadapaithankar/ARO-HCP
that referenced
this pull request
Feb 25, 2026
Picks up monitorV2ScopeBindingFile support in GenevaHealthStep (Azure/ARO-Tools#202) for multi-cloud Geneva monitor deployment.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
monitorV2ScopeBindingFilefield toGenevaHealthStepstruct, JSON schema, and test data__MONITORING_ACCOUNT_NAME__) in monitor JSONs with cloud-specific values from the scope binding fileContext
Part of the effort to consolidate Fairfax and Public Geneva monitors (ARO-22604/ARO-24790). Currently we maintain separate monitor folders per cloud in RP-GenevaConfig. With scope binding support, we can use a single shared set of monitors and parameterize cloud-specific differences at deploy time via EV2.
The follow-up work in sdp-pipelines will wire this field into the rollout parameter generation to produce the proper
monitorV2ScopeBindingFilepayload property withenableScopeTagBindings: true.Test plan
TestNewPipelineFromFilepasses with updated fixturespipelines/typestests pass