Description
/kind user-story
Which area this user story is related to?
/area registry
User Story
The registry viewer would need to be hosted at registry.devfile.io. Since the index endpoint is served at registry.devfile.io as well, we should serve the website when default (anything other than HTML and json) or html is requested, and the index json when json contents are requested
The registry viewer website could also be hosted on the same container running the index server devfile-index-base, since it is lightweight and we want to reduce the cost of maintaining two containers and can hold the logic for serving the appropriate content. The viewer and the registry will have the same update lifecycle.
Acceptance Criteria
- Create a Dockerfile layer that hosts the registry-viewer for the index server to interact with (@schultzp2020 )
- It should serve the appropriate content requested, html vs json (serve HTML for anything other than json on the request)
- Verify existing tools, e.g. odo, to make sure we don't introduce breakage to the existing product
- Ensure the registry library/tool providers are working as expected, as registry.devfile.io is expected to host the viewer
- Tekton pipelines and route definitions for staging/prod may need to be updated if it's exposed on a new port
Post:
- It should trigger the registry-support push next image workflow via a DISPATCH event (perhaps with a workflow on a new release)
Related Issue: #527