Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of VAULT-15840: Allow updates of only entity-alias custom-metadata into release/1.13.x #20440

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #20368 to be assessed for backporting due to the inclusion of the label backport/1.13.x.

The below text is copied from the body of the original PR.


With these changes, the following works. Previously, the final call would return an empty map:

$ vault auth enable userpass 
$ MA1=$(vault auth list -format=json | jq -r '."userpass/" | .accessor')
$ EID=$(vault write -field=id identity/entity name=max-winslow policies=entity-policy)
$ AID=$(vault write -field=id identity/entity-alias name=max1 canonical_id=$EID mount_accessor=$MA1)
$ vault write identity/entity-alias/id/$AID \
   - <<<'{"custom_metadata":{"foo":"bar"}}'
$ vault read -field=custom_metadata identity/entity-alias/id/$AID
map[foo:bar]

Closes #19434


Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/miagilepner/VAULT-15840-entity-alias-update-metadata/gladly-evolved-turkey branch from 1ed28d9 to e2fb250 Compare May 1, 2023 10:42
@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/miagilepner/VAULT-15840-entity-alias-update-metadata/gladly-evolved-turkey branch from c6193c7 to 71716b7 Compare May 1, 2023 10:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants