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.

Sign up for GitHub

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

Jump to bottom

Support apicurio as catalog for specifications #812

Closed
2 tasks done
jfallows opened this issue Feb 27, 2024 · 0 comments
Closed
2 tasks done

Support apicurio as catalog for specifications #812

jfallows opened this issue Feb 27, 2024 · 0 comments
Assignees
@bmaidics
Labels
story Feature description from user's perspective

Comments

@jfallows
Copy link
Contributor

jfallows commented Feb 27, 2024 •
edited
Loading

Describe the desired outcome from the user's perspective
As devops, I want to be able to store my OpenAPI and AsyncAPI specification in apicurio instead of on the filesystem relative to zilla.yaml.

Acceptance criteria

  • openapi specification can be retrieved from apicurio via catalog handler
  • asyncapi specification can be retrieved from apicurio via catalog handler

Tasks

Additional context
See apicurio rest api v3
@jfallows jfallows added the story Feature description from user's perspective label Feb 27, 2024
@jfallows jfallows mentioned this issue Feb 27, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bmaidics bmaidics

Labels
story Feature description from user's perspective
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jfallows @bmaidics