Reason/Context
From the inception days, microcksURL, keycloakClientId and keycloakClientSecret flags were required together but this came from a time where Microcks required authentication. This is no longer the case when using the uber distribution or with some setup on regular distribution.
However those flags are still mandatory and you can put random values (like foo and bar).
Description
We should set up these flags as optional and only mark keycloakClientId and keycloakClientSecret as must be defined together.
Implementation ideas
Adjust the flags properties in cmd.go
Reason/Context
From the inception days,
microcksURL,keycloakClientIdandkeycloakClientSecretflags were required together but this came from a time where Microcks required authentication. This is no longer the case when using the uber distribution or with some setup on regular distribution.However those flags are still mandatory and you can put random values (like
fooandbar).Description
We should set up these flags as optional and only mark
keycloakClientIdandkeycloakClientSecretas must be defined together.Implementation ideas
Adjust the flags properties in
cmd.go