Deployment lineage graph storage proposal#11848
Merged
Merged
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a design proposal describing a versioned “deployment lineage” graph that links deployed Radius resources back to the exact source artifacts (Bicep, params, recipes, env config) and forward from artifacts to all resulting deployments. This fits into the repo’s specs/ design/proposal area as a documentation-only exploration of future storage and query capabilities.
Changes:
- Add a proposal doc outlining a versioned graph model, current vs. future storage comparison, and high-level feature set.
- Add supporting design notes covering schema mapping concepts, runtime modes, serialization goals, and migration ideas.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| specs/003-git-app-graph-storage/radius-graph-proposal.md | Introduces the core “deployment lineage” versioned graph proposal and illustrative diagrams. |
| specs/003-git-app-graph-storage/design-notes.md | Adds background/design notes on graph projection, storage modes, schema mappings, and migration concepts. |
lakshmimsft
reviewed
Jun 3, 2026
Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
remove design-notes.md Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
brooke-hamilton
force-pushed
the
brooke-hamilton/radius-graph-storage
branch
from
e69ef98 to
87bcac3
Compare
nicolejms
approved these changes
Jun 15, 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.
Adds design documentation for storing and using a versioned application graph in Radius.
This PR covers:
The goal is to define a simple, extensible foundation for Radius deployment lineage and future graph-based workflows.