Skip to content

Discuss regarding merging meta.yaml and devfile.yaml #172

Closed
@GeekArthur

Description

@GeekArthur

Is your feature request related to a problem? Please describe.
Currently the registry index generator generates the index.json based on the fields in meta.yaml of each devfile component, we may need to use fields in devfile.yaml of each devfile component as well. Therefore, merging meta.yaml and devfile.yaml can help us centralize all the fields in one file then we can parse and generate index.json from one place.

Two things we need to discuss here:

  • Does meta.yaml has any special usage for consumers (eg. Che, odo)?
  • Is there anything that blocks us from merging meta.yaml and devfile.yaml?

Describe alternatives you've considered
Alternative 1:
We still use meta.yaml and devfile.yaml separately + DON'T ADD fields from meta.yaml to devfile.yaml (Today's version) -> we need to handle the case where there is a conflict exists between meta.yaml and devfile.yaml

Alternative 2:
We still use meta.yaml and devfile.yaml separately + ADD fields from meta.yaml to devfile.yaml -> only parse devfile.yaml then generate index.json

@elsony @davidfestal Please feel free to add questions and comments and we can discuss from there, thanks!

Metadata

Metadata

Assignees

Labels

area/registryDevfile registry for stacks and infrastructure

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions