Add Managed Apps app config JSON Schemas (v0.0) - #635
Open
Chamu Rajasekera (Chamu-Rajasekera) wants to merge 1 commit into
Open
Add Managed Apps app config JSON Schemas (v0.0)#635Chamu Rajasekera (Chamu-Rajasekera) wants to merge 1 commit into
Chamu Rajasekera (Chamu-Rajasekera) wants to merge 1 commit into
Conversation
Publish the ms.config.json and stage-overlay schemas for the Microsoft Apps CLI so editors can resolve them from an allowlisted developer.microsoft.com URL. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 45ea3c0d-f36b-42f3-9c07-fcb1f6657175
Chamu Rajasekera (Chamu-Rajasekera)
marked this pull request as ready for review
August 29, 2026 01:24
Pavan (pavankm)
approved these changes
Aug 31, 2026
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
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.
Publishes the two app configuration JSON Schemas used by the Microsoft Apps CLI (
ms) so that editors can resolve them from a stable, Microsoft-hosted URL.New files
managed-apps/ms-config/v0.0/schema.jsonmanaged-apps/stage-overlay/v0.0/schema.jsonms-configdescribesms.config.json, the base configuration file for a Microsoft App project (app identity, connection references, data sources, packaged schemas).stage-overlaydescribesms.<deployment>.config.json, a per-deployment overlay that overrides a subset of the base configuration when an app is promoted between environments.Both are JSON Schema draft-07. The version folder (
v0.0) matches theversionfield the schemas themselves pin, so future contract revisions land in a sibling folder and existing files keep resolving.Provenance
These files are generated, not hand-written. The source of truth is a set of Zod contracts in
@microsoft/managed-apps-common, rendered by a script in that package. A snapshot test in the owning repo fails if the generated output drifts from the reviewed contract, so the schemas here always match what the CLI actually enforces at runtime.Updates will follow the same path: regenerate from the contract, then open a PR here.
Why
The CLI currently emits a
$schemapointer at a raw GitHub URL. That is not in the defaultjson.schemasallowlist that VS Code trusts for automatic download, so users get no validation or completion in the editor without changing their settings.developer.microsoft.com/json-schemasis allowlisted, which is what this PR is for.Follow-up required before these URLs work
managed-appsis a new root-level folder. Per the repository README, a new root folder must be allowlisted by the developer app portal engineering team (devappportaleng@microsoft.com) so the locale segment is dropped from the public URL. Until that request is processed, the files will resolve athttps://developer.microsoft.com/json-schemas/en-us/managed-apps/...rather than the locale-free URLs listed above. I will send that request.Validation