Skip to content

Make keycloakClientId and keycloakClientSecret flags optional #209

@lbroudoux

Description

@lbroudoux

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions