Skip to content

feat(provider): add Azure App Configuration - #313

Open
itpropro wants to merge 13 commits into
cachix:mainfrom
itpropro:feat/azure-app-configuration-provider
Open

feat(provider): add Azure App Configuration#313
itpropro wants to merge 13 commits into
cachix:mainfrom
itpropro:feat/azure-app-configuration-provider

Conversation

@itpropro

@itpropro itpropro commented Aug 9, 2026

Copy link
Copy Markdown

Summary

  • add Azure App Configuration provider support for direct values, guarded writes/deletes, declaration discovery, exact labels, prefixes, tags, sovereign endpoints, and SecretSpec provider credentials
  • resolve canonical Azure Key Vault references with latest or pinned versions, deduplicated batch reads, and one or multiple authorized vaults
  • support Entra ID and connection-string authentication while keeping App Configuration and Key Vault identities independent
  • document 0.19+ configuration, deployment topologies, caching boundaries, security limits, and Entra-first authentication guidance

Scenario coverage

  • direct App Configuration values with null and exact labels, prefix/tag filters, and escaped filter characters
  • latest, pinned, duplicate, single-vault, and multi-vault Key Vault references
  • Entra and HMAC reads, filtered discovery, read-write CRUD, and read-only HMAC 403 enforcement
  • conditional writes/deletes, pagination, Sync-Token propagation, malformed responses, selector refusal, and bounded multi-vault behavior through protocol tests

Validation

  • cargo test --all
  • focused Azure App Configuration, Azure Key Vault, and generic provider suites
  • devenv shell -- prek run -a
  • npm --prefix docs run build (74 pages)
  • authenticated Azure validation against App Configuration and two Key Vaults; all fixtures removed and local authentication restored to disabled
  • independent clean-context GPT-5.6 Sol xhigh review: no actionable findings

Live denied-vault batch failure, service pagination, concurrent ETag races, and observed Sync-Token variants remain protocol-tested rather than service-observed.

@itpropro
itpropro marked this pull request as ready for review August 9, 2026 15:49
@itpropro

itpropro commented Aug 9, 2026

Copy link
Copy Markdown
Author

@domenkozar would like to hear your thoughts on this, anything that needs improvement?

@domenkozar

Copy link
Copy Markdown
Member

Needs a rebase, hoping for someone that uses Azure to give it a spin :)

@itpropro

Copy link
Copy Markdown
Author

Needs a rebase, hoping for someone that uses Azure to give it a spin :)

I'll do the rebase. It is already tested against Azure, I implemented it because I am using Azure ;)
Tested it against a live environment with multiple read only identities and app config only, app config + key vault and app config + multiple key vault references with different identities for both.

@itpropro
itpropro force-pushed the feat/azure-app-configuration-provider branch from 36a7c02 to ba61079 Compare August 10, 2026 08:38
@itpropro

Copy link
Copy Markdown
Author

Rebased @domenkozar

@itpropro

Copy link
Copy Markdown
Author

@domenkozar anything else I can do/fix?

@domenkozar

Copy link
Copy Markdown
Member

I'll take a look soon, could you rebase please?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants