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

The registry should have a headless REST API server build option #977

Closed
schultzp2020 opened this issue Oct 26, 2022 · 2 comments · Fixed by devfile/registry-support#147
Closed
Assignees
Labels
area/registry Devfile registry for stacks and infrastructure

Comments

@schultzp2020
Copy link
Contributor

schultzp2020 commented Oct 26, 2022

Which area this feature is related to?

/area registry

Which functionality do you think we should add?

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

As a consumer of the registry REST API, I should have the option to spin up a headless REST API server.

Detailed description:

The only difference between the headed and headless REST API server is that the headless REST API server does not include the registry viewer.

Describe the solution you'd like

A build arg should be passed to build either a headed or headless build of the REST API server.

Describe alternatives you've considered

N/A

Additional context

N/A

Target Date: 11-08-2022

@openshift-ci openshift-ci bot added the area/registry Devfile registry for stacks and infrastructure label Oct 26, 2022
@michael-valdron michael-valdron self-assigned this Oct 26, 2022
@michael-valdron
Copy link
Member

Already tackling this task along side #747

@michael-valdron
Copy link
Member

michael-valdron commented Nov 1, 2022

blocked by devfile/devfile-web#51 Unblocked

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/registry Devfile registry for stacks and infrastructure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants