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

Fix OpenAPI spec definitions for PKI EAB APIs #21458

Merged
merged 2 commits into from
Jun 27, 2023

Conversation

stevendpclark
Copy link
Contributor

  • 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

 - 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
@stevendpclark stevendpclark added this to the 1.14.1 milestone Jun 26, 2023
@stevendpclark stevendpclark requested review from averche and a team June 26, 2023 18:58
@stevendpclark stevendpclark self-assigned this Jun 26, 2023
Copy link
Contributor

@averche averche left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing this!

For future reference, these are the new EAB OpenAPI OperationIDs:

Path Method OperationID
/{pki_mount_path}/eab get pki-list-eab-keys
/{pki_mount_path}/eab/{key_id} delete pki-delete-eab-key
/{pki_mount_path}/acme/new-eab post pki-generate-eab-key
/{pki_mount_path}/issuer/{issuer_ref}/acme/new-eab post pki-generate-eab-key-for-issuer
/{pki_mount_path}/issuer/{issuer_ref}/roles/{role}/acme/new-eab post pki-generate-eab-key-for-issuer-and-role
/{pki_mount_path}/roles/{role}/acme/new-eab post pki-generate-eab-key-for-role

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants