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 Introduce high privilege namespace (administrative namespace) into release/1.13.x #21608

Conversation

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

Backport

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

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@biazmoreira
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/vault/merges: 409 Merge conflict []

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


Full functionality only works in enterprise. This adds the core implementation pieces needed.


Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/biazmoreira/high-privilege-namespace/similarly-vast-bonefish branch from ac380ce to 88bd648 Compare July 6, 2023 07:52
@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/biazmoreira/high-privilege-namespace/similarly-vast-bonefish branch from 88bd648 to ac380ce Compare July 6, 2023 07:52
@hashicorp-cla
Copy link

hashicorp-cla commented Jul 6, 2023

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes


1 out of 2 committers have signed the CLA.

  • biazmoreira
  • temp

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.

Have you signed the CLA already but the status is still pending? Recheck it.

@biazmoreira biazmoreira marked this pull request as ready for review July 6, 2023 09:06
@biazmoreira biazmoreira added this to the 1.13.5 milestone Jul 6, 2023
@VioletHynes VioletHynes added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Jul 6, 2023
@tomcf-hcp
Copy link
Collaborator

Closing this pull request. Completed with this pull request: #21647

@tomcf-hcp tomcf-hcp closed this Jul 26, 2023
@calvn calvn deleted the backport/biazmoreira/high-privilege-namespace/similarly-vast-bonefish branch July 26, 2023 23:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants