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

Automation for providing a OpenAPI compatible devfile spec for the devfile registry #1146

Open
michael-valdron opened this issue Jun 27, 2023 · 3 comments
Labels
area/api Enhancement or issue related to the api/devfile specification area/ci area/registry Devfile registry for stacks and infrastructure lifecycle/stale Stale items. These items have not been updated for 90 days.

Comments

@michael-valdron
Copy link
Member

Which area this feature is related to?

/area ci
/area api
/area registry

Which functionality do you think we should add?

Why is this needed? Is your feature request related to a problem?

In order to reference the devfile specification as a schema to use under the RESTful OpenAPI specification for the devfile registry, OpenAPI 3 compatibility for the devfile specification is needed.

Detailed description:

The OpenAPI 3 specification for the REST API being added as part of #972 benefits by providing type and endpoint definition source generation as well as REST API documentation #1145. To extend these benefits such as extending generated docs and allow type generation to clients which do not use Go such as the registry viewer #957, we need an OpenAPI compatible devfile specification for the RESTful OpenAPI specification to reference.

Describe the solution you'd like

Due to this being a specific need of the devfile registry, we can solve this by using CI automation which captures the version of the devfile specification used by the devfile registry and provides a converted copy to the registry-support repository which can be referenced by the RESTful OpenAPI specification.

Describe alternatives you've considered

An alternative would be to generate the devfile specification with OpenAPI 3 compatibility from the API source. This would require additional work to be done to change the way the devfile specification is currently being generated along with any necessary changes to the devfile library or parser.

Additional context

@openshift-ci openshift-ci bot added area/ci area/api Enhancement or issue related to the api/devfile specification area/registry Devfile registry for stacks and infrastructure labels Jun 27, 2023
@michael-valdron michael-valdron moved this to Need triage in Devfile Project Jun 27, 2023
@michael-valdron michael-valdron moved this to Backlog in Devfile Project Jul 27, 2023
@github-actions
Copy link

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.

@github-actions github-actions bot added the lifecycle/stale Stale items. These items have not been updated for 90 days. label Oct 24, 2023
@michael-valdron michael-valdron moved this from Backlog to Refinement in Devfile Project Nov 28, 2023
@michael-valdron
Copy link
Member Author

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.

Should be planned at some point.

@github-actions github-actions bot removed the lifecycle/stale Stale items. These items have not been updated for 90 days. label Sep 19, 2024
Copy link

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 120 days.

@github-actions github-actions bot added the lifecycle/stale Stale items. These items have not been updated for 90 days. label Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/api Enhancement or issue related to the api/devfile specification area/ci area/registry Devfile registry for stacks and infrastructure lifecycle/stale Stale items. These items have not been updated for 90 days.
Projects
Status: Refinement
Development

No branches or pull requests

2 participants