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 Remove duplicated allow_empty_principals parameter in role api docs into release/1.17.x #28581

Conversation

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

Backport

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

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


Description

https://developer.hashicorp.com/vault/api-docs/secret/ssh#create-update-role has the allow_empty_principles defined twice within the same section. Remove one keeping the definition

[allow_empty_principals](https://developer.hashicorp.com/vault/api-docs/secret/ssh#allow_empty_principals) (bool: false) - Allow signing certificates with no valid principals (e.g. any valid principal). For backwards compatibility only. The default of false is highly recommended.

TODO only if you're a HashiCorp employee

  • Backport Labels: If this PR is in the ENT repo and needs to be backported, backport
    to N, N-1, and N-2, using the backport/ent/x.x.x+ent labels. If this PR is in the CE repo, you should only backport to N, using the backport/x.x.x label, not the enterprise labels.
    • If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
  • ENT Breakage: If this PR either 1) removes a public function OR 2) changes the signature
    of a public function, even if that change is in a CE file, double check that
    applying the patch for this PR to the ENT repo and running tests doesn't
    break any tests. Sometimes ENT only tests rely on public functions in CE
    files.
  • Jira: If this change has an associated Jira, it's referenced either
    in the PR description, commit message, or branch name.
  • RFC: If this change has an associated RFC, please link it in the description.
  • ENT PR: If this change has an associated ENT PR, please link it in the
    description. Also, make sure the changelog is in this PR, not in your ENT PR.

Overview of commits

@stevendpclark stevendpclark enabled auto-merge (squash) October 3, 2024 13:55
Copy link

github-actions bot commented Oct 3, 2024

CI Results:
All Go tests succeeded! ✅

Copy link

github-actions bot commented Oct 3, 2024

Build Results:
All builds succeeded! ✅

@stevendpclark stevendpclark merged commit 016d484 into release/1.17.x Oct 3, 2024
34 of 36 checks passed
@stevendpclark stevendpclark deleted the backport/docs/stevendpclark/remove-duplicate-param/strangely-loved-kodiak branch October 3, 2024 13:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport docs hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed pr/no-changelog pr/no-milestone
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants