You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently the registry index generator generates the
index.json
based on the fields inmeta.yaml
of each devfile component, we may need to use fields indevfile.yaml
of each devfile component as well. Therefore, mergingmeta.yaml
anddevfile.yaml
can help us centralize all the fields in one file then we can parse and generateindex.json
from one place.Two things we need to discuss here:
meta.yaml
has any special usage for consumers (eg. Che, odo)?meta.yaml
anddevfile.yaml
?Describe alternatives you've considered
Alternative 1:
We still use
meta.yaml
anddevfile.yaml
separately + DON'T ADD fields frommeta.yaml
todevfile.yaml
(Today's version) -> we need to handle the case where there is a conflict exists betweenmeta.yaml
anddevfile.yaml
Alternative 2:
We still use
meta.yaml
anddevfile.yaml
separately + ADD fields frommeta.yaml
todevfile.yaml
-> only parsedevfile.yaml
then generateindex.json
@elsony @davidfestal Please feel free to add questions and comments and we can discuss from there, thanks!
The text was updated successfully, but these errors were encountered: