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 UI: Allow token configuration tune from namespace into release/1.15.x #24150

Conversation

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

Backport

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

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


The previous PR that fixed this issue only did so for non-namespace token mounts. We didn't realize ns_token was a token type, so this checks the correct model attribute with ns_ stripped away


Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/VAULT-22043/token-type-disallow-ns/instantly-growing-fowl branch from 30e5521 to 3b9627c Compare November 15, 2023 22:19
@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/VAULT-22043/token-type-disallow-ns/instantly-growing-fowl branch from c12a2aa to 35ce37a Compare November 15, 2023 22:19
@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Nov 15, 2023
@hashishaw hashishaw added this to the 1.15.3 milestone Nov 15, 2023
Copy link

Build Results:
All builds succeeded! ✅

@hashishaw hashishaw merged commit afa2bb3 into release/1.15.x Nov 15, 2023
63 of 66 checks passed
@hashishaw hashishaw deleted the backport/VAULT-22043/token-type-disallow-ns/instantly-growing-fowl branch November 15, 2023 23:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed ui
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants