Naming of CheCluster Custom Resource server devfileRegistryUrl
and status devfileRegistryURL
is confusing and error prone
#19632
Labels
area/che-operator
Issues and PRs related to Eclipse Che Kubernetes Operator
kind/task
Internal things, technical debt, and to-do tasks to be performed.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
severity/P2
Has a minor but important impact to the usage or development of the system.
Describe the bug
Looks like #19627 wasn't a bug.
devfileRegistryURL
instead ofdevfileRegistryUrl
. However this is errorprone. Same for thepluginRegistryUrl
: I had that issue 3 weeks ago not knowing what was wrong ... but probably the same problemAnd broker not able to download plugins from the registry.
We cannot keep the "almost" the same names for these. Either they are the same, or we should use completely different names to avoid errors.
Che version
Steps to reproduce
See #19627
Expected behavior
Maybe
status.devfileRegistryURL
should be renamedstatus.devfileRegistryUrl
. (andstatus.pluginRegistryURL
renamedstatus.pluginRegistryUrl
) that would avoid error from the user.Runtime
kubectl version
)oc version
)minikube version
andkubectl version
)minishift version
andoc version
)docker version
andkubectl version
)Screenshots
Installation method
chectl version
commandEnvironment
Eclipse Che Logs
Additional context
The text was updated successfully, but these errors were encountered: