refactor: one place for Key Vault collections and paging in the providers #75

Merged

keb merged 1 commits from refactor/provider-duplication into main

2026-10-15 10:41:43 +02:00

Author	SHA1	Message	Date
keb	114478d2f2	refactor: one place for Key Vault collections and paging in the providers CI / Checks (pull_request) Successful in 40s Details PR title / Conventional title (pull_request) Successful in 1s Details - ObjectType.Collection names a type's segment in Key Vault URLs and links (secrets, keys, certificates), instead of four copies in ref, azure and fake. - Azure lists through one pager helper instead of eight hand-written page loops; Value is VersionedValue without the version, rather than the two calling each other. - Databricks' Key Vault fallback check lives in fallbackVault. - The repo provider reads .lazysecrets.yaml in one place, builds plain and sops objects in one loop, and parses a file's sops metadata from the bytes Objects already read.	2026-10-15 10:40:41 +02:00

Author

SHA1

Message

Date

keb

114478d2f2

refactor: one place for Key Vault collections and paging in the providers

CI / Checks (pull_request) Successful in 40s

Details

PR title / Conventional title (pull_request) Successful in 1s

Details

- ObjectType.Collection names a type's segment in Key Vault URLs and links (secrets, keys, certificates), instead of four copies in ref, azure and fake.
- Azure lists through one pager helper instead of eight hand-written page loops; Value is VersionedValue without the version, rather than the two calling each other.
- Databricks' Key Vault fallback check lives in fallbackVault.
- The repo provider reads .lazysecrets.yaml in one place, builds plain and sops objects in one loop, and parses a file's sops metadata from the bytes Objects already read.

2026-10-15 10:40:41 +02:00