Use specific command name instead of generic init-container-command
in plugin-registry devfiles
#19495
Labels
area/plugin-registry
kind/enhancement
A feature request - must adhere to the feature request template.
severity/P2
Has a minor but important impact to the usage or development of the system.
Is your enhancement related to a problem? Please describe.
Today, plugin-registry is generating from meta.yaml files devfile.yaml but they all have
init-container-command
as command name. So there is high risk of conflict.Describe the solution you'd like
We should generate specific name like
init-remote-runtime-injector
instead of the same nameDescribe alternatives you've considered
make specific command when #19034 is implemented
Additional context
The text was updated successfully, but these errors were encountered: