docs(vault-config): document providerConfigKind and bump KCL module reference#71
Merged
patrick-hermann-sva merged 1 commit intofeat/vault-config-bump-xplane-kcl-0.5.0from Apr 14, 2026
Conversation
…eference to 0.5.0 - Add Provider Config section documenting providerConfigName and the new providerConfigKind field introduced with xplane-vault-config 0.5.0 - Update Dependencies to reference the current KCL module version 0.5.0
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
1 participant
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.
Summary
Docs-only follow-up to #70. The PR only touches
apis/but leaves the README inconsistent with the XRD and composition changes.configurations/bootstrap/vault-config/README.mddocumenting:providerConfigName(was previously undocumented)providerConfigKindfield (defaultClusterProviderConfig, enumClusterProviderConfig/ProviderConfig) introduced withxplane-vault-config0.5.0 for v2 namespaced MR provider ref handlingoci://ghcr.io/stuttgart-things/xplane-vault-config:0.1.0→0.5.0(matchesapis/composition.yaml)Not changed (intentional)
examples/claim.yaml,examples/development.yaml,examples/production.yaml— the new field is optional with a sensible default, so existing examples still render correctly and don't need updates. ForcingproviderConfigKindinto every example would just be noise.Test plan
apis/composition.yamlalready usesxplane-vault-config:0.5.0so the new dependency reference is accuratecrossplane renderbehavior from feat(vault-config): bump xplane-vault-config KCL module to 0.5.0 #70 is unaffectedStacked on top of #70.
Generated with Claude Code