Repository navigation
Fix/azure access data actions rebased - #98
Merged
amansingh39 merged 2 commits intoOct 23, 2026
Merged
Conversation
…lt, Service Bus, Event Hubs) A block on a Foundry project's identity left its agent answering: the agent reads an Azure AI Search index with Search Index Data Reader, a role with data actions only, and a block outside storage accounts looked at management actions only. azureActions now adds the data actions (and key listings) of AI Search, Key Vault secrets, Service Bus and Event Hubs; an allow assigns Search Index Data Reader/Contributor and Key Vault Secrets User/Officer there. Storage accounts and every other resource type are unchanged. The preview notes AI Search API keys and Key Vault access policies, which role assignments do not cover. Tests: TestAzureActions*, TestAzureBlockReachesSearchIndexData, TestAzureAllowAssignsDataRoles, TestAzureDataPlaneChildTypes, TestAccessPolicyAzureSearchIndex. Existing Azure and AWS access-policy tests still pass.
…a role Reader and Contributor reach no message, so an allow there read Active while the identity still could not send or receive. An allow now assigns Azure Service Bus / Event Hubs Data Receiver (read), Data Sender (write), or Data Owner (read and write). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
apauthnull
pushed a commit
that referenced
this pull request
Oct 24, 2026
Staging's PR #98 added an Azure data-plane table (AI Search, Key Vault, Service Bus, Event Hubs) under the same names as this branch's fuller one in services/iga_gov_access_azure_planes.go. Resolution: - keep this branch's table; drop the duplicate type, table, lookup, azureActions addition and per-type note from iga_gov_access_azure.go; - adopt #98's allow of read and write on Service Bus / Event Hubs: Data Owner (bothRole), with a preview warning that it also manages the namespace (this branch had refused it); - role constants: this branch's plus #98's two Data Owner roles; - #98's unit tests adapted where this branch deliberately differs (a storage account block covers every data service and SAS path; a mapped type's read is its data and key actions, not the management read); its integration test runs unchanged; - docs/PROGRESS.md keeps both histories. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Description
Changes
Testing
go test -short ./tests/unit/)go vet ./...cleanrun-integrationto this PR to trigger integration tests in CI (requires a live DB)Checklist