Bump vault-secrets-arrstack provider to 0.2.0 and plumb methods #145
Reference in New Issue
Block a user
Delete Branch "benvin/arrstack-provider-0.2.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
Engine plugin v0.2.0 (catalog bumped in #144) added a
methodsfield to arrstack roles, pinning a minted arrproxy key to a set of HTTP methods so a read-only integration can hold a key that cannot write. Provider v0.2.0 (just published to theterraform-unkinregistry) exposes it as an optional set attribute, but the module had no input for it, so no role yaml could use it.How
vault-secrets-arrstackprovider pin from 0.1.1 to 0.2.0 inenvironments/root.hcland both arrstack modules.methodsinput tomodules/vault_cluster/modules/arrstack_secret_backend_roleand passes it through to the resource.methodsthrough thevault_clusterarrstack_secret_backend_roleobject type, so a role yaml may now carry amethods:list and it flows via the existing config.hcl merge with no discovery change.methodsdefaults tonullrather than[]: the provider reads an unrestricted role back as null, so a null default keeps a role yaml that omits the field drift-free. An empty-set default would plannull -> []on every existing role.Expected plan: no resource changes. No role yaml changes here, so the plan should be a provider-version-only diff (provider upgrade, zero add/change/destroy).
Follow-up PR scopes the mediamark role to GET/HEAD.