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 Fix OpenAPI spec definitions for PKI EAB APIs into release/1.14.x #21468

Conversation

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

Backport

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

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


  • Do not generate duplicate operation ids for the various new-eab apis
  • Fill out proper operation verb for eab delete call
  • Pluralize operation verb for list-eab-keys api
  • Fill out proper response data for new-eab and list-eab-keys

Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core requested a review from a team June 27, 2023 12:44
@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/stevendpclark/vault-17538-fix-eab-openapi-spec/partially-tolerant-poodle branch from 9bd7bba to 8890a7b Compare June 27, 2023 12:44
@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/stevendpclark/vault-17538-fix-eab-openapi-spec/partially-tolerant-poodle branch from ba569f5 to 1e946b8 Compare June 27, 2023 12:44
@stevendpclark stevendpclark self-assigned this Jun 27, 2023
@stevendpclark stevendpclark enabled auto-merge (squash) June 27, 2023 12:45
@stevendpclark stevendpclark merged commit 33c7b16 into release/1.14.x Jun 27, 2023
@stevendpclark stevendpclark deleted the backport/stevendpclark/vault-17538-fix-eab-openapi-spec/partially-tolerant-poodle branch June 27, 2023 13:14
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