Description of problem: This request proposes to make the "oc" client extensible by means of adding a plugin architecture to it.
Agree. We need to publish how to extend the go client. That will not happen in OSE 3.1.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
It would be helpful to elaborate on what types of extension points would be useful.
Not a plugin architecture, but having a generic way to insert object attributes via JSONPath/YamlPath(?) expressions would be extremely useful; something to the effect of allowing "--attribute spec.source.sourceSecret.name=gitlabsecret" that would add that node to the corresponding object
This has been delivered at Tech Preview in 3.7 and planned supported in upcoming release.
(In reply to Steve Speicher from comment #12) > This has been delivered at Tech Preview in 3.7 and planned supported in > upcoming release. Steve, I wasn't able to find a mention on the release notes (under Tech Preview section), is there anything I could point my customers to ? Thanks.
Not sure why it isn't in release notes but reading https://docs.openshift.com/container-platform/3.7/cli_reference/extend_cli.html
(In reply to Steve Speicher from comment #14) > Not sure why it isn't in release notes but reading > https://docs.openshift.com/container-platform/3.7/cli_reference/extend_cli. > html thanks, I've just forwarded the link to the customer and waiting for their feedback.
I'm changing assignee to Michal, since he's in charge of master team. We should have alpha version along with the rebase in 4.0. Beta, iow. more stable with the next rebase to 1.13.
This mechanism will be available as of 4.0.
This landed with the rebase, moving to QA.
This is provided as part of 4.1 (in a technology preview state).