Refresh FinOps hub upgrade procedure for multi-version FOCUS adoption#2123
Refresh FinOps hub upgrade procedure for multi-version FOCUS adoption#2123flanakin wants to merge 3 commits intoflanakin/focus14from
Conversation
…#2121) Update the canonical "add a new FOCUS version" procedure to reflect the six additional steps surfaced during FOCUS 1.4 scoping (Cost Management dependency check, open-data metadata, conformance regen, plugin updates, changelog) and add guidance for handling two FOCUS versions in one cycle (GA + preview). Clarify the hub-schema-to-FOCUS-version relationship and preview convention in data-model.md. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
microsoft-github-policy-service
Bot
added
the
Needs: Review 👀
There was a problem hiding this comment.
Pull request overview
Refreshes the FinOps hubs documentation playbook for adding new FOCUS versions, with explicit guidance for preview vs GA handling and a clearer explanation of how hub schema versions relate to FOCUS spec versions.
Changes:
- Expanded the “add a new FOCUS version” procedure with dependency checks, open-data metadata, conformance regeneration, plugin reference updates, and changelog guidance.
- Added guidance for handling two FOCUS versions in a single release cycle (GA + preview) and keeping unversioned functions pinned to latest GA.
- Clarified in user docs that hub schema versions mirror the FOCUS version they natively ingest, and documented the preview convention.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| src/templates/finops-hub/docs/README.md | Updates the canonical upgrade procedure and adds multi-version (GA + preview) guidance. |
| docs-mslearn/toolkit/hubs/data-model.md | Clarifies schema-version-to-FOCUS coupling and documents preview behavior for hub schemas. |
| | 12+ | `v1_2` | 1.2 | | ||
| | 0.7-11 | `v1_0` | 1.0 | | ||
|
|
||
| When hub support ships ahead of a FOCUS specification ratifying or ahead of Cost Management exporting a version, the hub schema is labeled **preview**. Preview schemas may change without notice between releases. The unversioned functions remain pinned to the latest GA schema until the preview promotes to GA, ensuring production reports stay stable while early adopters validate the new version. |
There was a problem hiding this comment.
🤖 [AI][Claude Code] ✅ Implemented
Reworded to "ahead of FOCUS specification ratification" for parallel structure with the next clause.
Conformance reports are generated only against official Microsoft Cost Management FOCUS releases, not as part of adding a new FOCUS version to FinOps hubs. Removing the step keeps the procedure scoped to the hub-specific workstream. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
🤖 [AI][Claude Code] Additional change beyond Copilot review While addressing the grammar fix on Updated both
Phase 4 ( |
- Reword data-model.md:66 grammar (per Copilot). - Decouple hub preview status from Cost Management export availability. Preview now means the FOCUS spec is still working draft. Cost Management lag is a separate operational concern that does not gate hub GA. - Update README step 0 to match. Co-Authored-By: copilot-pull-request-reviewer <copilot-pull-request-reviewer@users.noreply.github.com> Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
🤖 [AI][Claude Code] PR Update Summary Addressed: 1 review thread + scope expansion
|
Summary
Phase 0 of FOCUS 1.4 work (parent: #2120). Refreshes the canonical "add a new FOCUS version" procedure before any 1.3/1.4 schema work begins, so subsequent phases follow a consistent, version-agnostic playbook.
Changes
src/templates/finops-hub/docs/README.mdBuild-FocusConformance.ps1, plugin skill file updates (5 listed paths), changelog entry.docs-mslearn/toolkit/hubs/data-model.mdNo FOCUS 1.3/1.4-specific content lands here — that's tracked in later phases.
Closes #2121
Test plan