Repository navigation
docs: access policies and the graph as built and live - #99
Merged
Merged
Conversation
- SPEC-access-policies: status (AWS and Azure built and in production, Azure verified end to end on 2026-10-22); each screen marked built, with where the build differs from the plan; the graph section as shipped (shared read, assignment cards, Summary/Detailed/Paths, policy from the selection card, block marks); the demo as it runs from the graph; a new section 6 with what is verified and the known limits. - SPEC-iga-phase2-graph 5.4: the traversal routes serve Kubernetes and Azure too (D-107 to D-114); the lists stay AWS. - AGENTS.md: where the graph providers, access policies and the no-switch schema rule live; check 001_bootstrap.sql on its own, not only fresh vs upgraded.
Ritam's 4f7b12e/5a1ba7bc: a block also removes data-plane roles on AI Search, Key Vault, Service Bus and Event Hubs, and an allow assigns their data role. Section 1 gets the role table; section 6 notes that API keys and Key Vault access policies are not covered and that the console names these data roles by id.
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.
Documentation only (no code).
SPEC-access-policies.md: AWS and Azure built and in production; screens marked built with where the build differs from the plan; the graph as shipped (shared read, assignment cards, Summary/Detailed/Paths, policy from the selection card, block marks); the demo as it runs; section 6, verified and known limits; the Azure data planes a policy reaches (AI Search, Key Vault, Service Bus, Event Hubs, from Fix/azure access data actions rebased #98).SPEC-iga-phase2-graph.md5.4: the traversal routes serve Kubernetes and Azure too; the lists stay AWS.AGENTS.md: graph providers, access policies, the no-switch schema rule, and checking001_bootstrap.sqlon its own.🤖 Generated with Claude Code