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

Add support for Service Catalog #61

Closed
YasithD opened this issue Jul 8, 2024 · 1 comment
Closed

Add support for Service Catalog #61

YasithD opened this issue Jul 8, 2024 · 1 comment

Comments

@YasithD
Copy link

YasithD commented Jul 8, 2024

Description:
Currently the OpenAPI definitions, which are generated or reused (when it is used to create the API) are stored in the directory resources/api-definitions. While this is a good place to store these files thinking from an user point of view, the MI server expects files to be in a certain format (two files _swagger and _metadata per each API) which is stored in the resources/metadata directory to provide APIM support through the Service Catalog.

We should rethink this experience and try to get users towards the resource/api-definitions structure while providing the necessary APIM support. This will include things such as,

  • Ideal ways to store the _swagger and _metadata files.
  • Ideal ways to version the swaggers.
  • A way to link the API to the swagger.
  • Generating missing swaggers at build time, etc.

Suggested Labels:

Suggested Assignees:

Affected Product Version:

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

@ChinthakaJ98
Copy link

This issue will be further tracked via #332 as they mention the same concern.

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

No branches or pull requests

3 participants