fix(stg-global): create V2 Grafana on supported major version via stgGlobalV2.grafanaMajorVersion (AROSLSRE-1362)

[hbhushan3]

What

Adds a transient, V2-only stgGlobalV2.grafanaMajorVersion config value (empty-sentinel default; 13 for stg in the MSFT overlay) and points the parallel STG-global "V2" Grafana deployment at it, instead of the shared monitoring.grafanaMajorVersion.

• config/config.schema.json — new grafanaMajorVersion property + required entry on the stgGlobalV2 object.
• config/config.yaml — grafanaMajorVersion: "empty-sentinel" default (so every cloud/env resolves under missingkey=error).
• config/config.msft.clouds-overlay.yaml — real value grafanaMajorVersion: "13" for stg.
• dev-infrastructure/configurations/global-infra-stg.tmpl.bicepparam — rewires param grafanaMajorVersion from {{ .monitoring.grafanaMajorVersion }} → {{ .stgGlobalV2.grafanaMajorVersion }}.
• config/rendered/** — regenerated via make -C config/ materialize.

This mirrors the existing stgGlobalV2.grafanaName pattern (added in #5813) one-for-one.

Why

Azure Managed Grafana retired Grafana 11 for new workspace creation on 2026-06-15 — new workspaces on the Standard SKU now only accept major version 12 or 13. The STG-global V2 migration creates a brand-new Grafana workspace in a dedicated subscription, so it hit:

GrafanaMajorVersionNotSupported: major version '11' not valid for sku Standard. Valid: 12, 13

The shared monitoring.grafanaMajorVersion is still "11", which is correct for the existing, grandfathered live fleet (Azure auto-upgrades those 11 → 12 in place). We must not bump the shared value just to unblock the new V2 workspace — that would force an irreversible, breaking 11 → 12 upgrade on the live fleet.

A V2-only override keeps the two concerns separate:

• Live fleet stays on the shared monitoring.grafanaMajorVersion (11, grandfathered).
• New V2 workspace is born on 13 via stgGlobalV2.grafanaMajorVersion.

(The broader "keep the shared value on a supported release" hygiene is tracked separately in AROSLSRE-1364.)

Testing

• Direct Azure validation — created a throwaway workspace on the exact SKU the bicep hardcodes (Standard) at major version 13; provisioning succeeded:

  az grafana create -n arohcp-g13-test -g hbhushan-test -l uksouth \
    --grafana-major-version 13 --sku Standard
  # -> provisioningState: Succeeded, grafanaVersion: 13.0.2, sku: Standard
  

  Confirms a fresh STG-global V2 workspace can be created on 13. (11 → 13 in-place upgrade is not a documented path, but fresh creation on 13 is — which is what V2 does.)
• make -C config/ materialize passes; schema is valid JSON.
• Render check — stgGlobalV2.grafanaMajorVersion resolves to empty-sentinel in all dev renders (dev gets no stg overlay); the real 13 is supplied by the MSFT overlay and surfaces in the downstream (sdp-pipelines) stg render, exactly like stgGlobalV2.grafanaName.
• All stgGlobalV2.* values remain consumed only by the stg/uksouth-only V2 pipelines; empty-sentinel is never deployed.

Notes / follow-up

• Transient: the entire stgGlobalV2 block (including this field) is removed at migration decommission.
• Sequencing with grafanactl (chore(grafana): move workspace lookup to pipeline shell step (ARO-28040) #5837): this rewires the bicepparam path. When chore(grafana): move workspace lookup to pipeline shell step (ARO-28040) #5837 moves Grafana creation to the grafanactl reconcile shell step, the new GRAFANA_MAJOR_VERSION configRef must be re-pointed from monitoring.grafanaMajorVersion → stgGlobalV2.grafanaMajorVersion as well. The config field added here stays valid across that change; only the wiring relocates.

Refs: AROSLSRE-1362. Follows #5813 (stgGlobalV2.grafanaName).

[Copilot]

Pull request overview

This PR introduces a V2-only override for Azure Managed Grafana major version in the transient stgGlobalV2 config block, so the STG-global V2 deployment can create a new Grafana workspace on a supported major version without changing the shared monitoring.grafanaMajorVersion used by the existing fleet.

Changes:

• Add stgGlobalV2.grafanaMajorVersion to config schema + defaults (empty-sentinel) and set it to "13" in the MSFT stg overlay.
• Rewire the STG-global V2 bicepparam (global-infra-stg.tmpl.bicepparam) to use stgGlobalV2.grafanaMajorVersion instead of monitoring.grafanaMajorVersion.
• Regenerate rendered dev config outputs to include the new key under stgGlobalV2.

Reviewed changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
dev-infrastructure/configurations/global-infra-stg.tmpl.bicepparam	Points V2 STG global-infra deployment at stgGlobalV2.grafanaMajorVersion for workspace creation.
config/config.schema.json	Adds grafanaMajorVersion to stgGlobalV2 schema and marks it required.
config/config.yaml	Adds stgGlobalV2.grafanaMajorVersion: empty-sentinel default to satisfy missingkey=error rendering.
config/config.msft.clouds-overlay.yaml	Supplies the real stg value ("13") for stgGlobalV2.grafanaMajorVersion.
config/rendered/dev/pers/westus3.yaml	Materialized dev render updated with stgGlobalV2.grafanaMajorVersion.
config/rendered/dev/perf/westus3.yaml	Materialized dev render updated with stgGlobalV2.grafanaMajorVersion.
config/rendered/dev/dev/westus3.yaml	Materialized dev render updated with stgGlobalV2.grafanaMajorVersion.
config/rendered/dev/cspr/westus3.yaml	Materialized dev render updated with stgGlobalV2.grafanaMajorVersion.
config/rendered/dev/ci01/centralus.yaml	Materialized dev render updated with stgGlobalV2.grafanaMajorVersion.
config/rendered/dev/ci00/centralus.yaml	Materialized dev render updated with stgGlobalV2.grafanaMajorVersion.

[raelga]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hbhushan3, raelga

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• config/OWNERS [hbhushan3,raelga]
• dev-infrastructure/OWNERS [hbhushan3,raelga]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-merge-bot]

/retest-required

Remaining retests: 0 against base HEAD e4ba38e and 2 for PR HEAD 1073b00 in total