Define canonical properties for surfacing ARM metadata
Open
@michaeltlombardi is already working on this.
Since Jan 22, 2026.
Doc-Impact
Issue-Enhancement
Partner-MC
Schema-Impact
- Dominant language
- Rust
- Stars
- 523
- Forks
- 75
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 24
Description
Summary of the new feature / enhancement
Related to #598 and #884, we need to define canonical properties for resources to use that can be surfaced in an ARM context.
Currently, we need to define:
_name- the uniquely identifying name for an instance. According to the ARM documentation, the name must follow URI component restrictions defined in RFC3986._securityContext- indicates the requisite security context for managing the instance. Must be valid for thesecurityContextmetadata property._kind- Indicates a subtype for the resource when a resource supports multiple object forms validated by different JSON subschemas. This can be an arbitrary string.
Proposed technical implementation details (optional)
We'll need to define each of these canonical properties as JSON Schemas, include them in the published schemas, and document them.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.