I have a working operator with a collection/component configuration
I want to add a standalone workload to this operator
I run the operator-builder create api command to add the standalone workload
Because the CLI is initially scaffolded during init, it errors out
Making the companionCliRootcmd match the existing command with work, but the pathing is wonky (mycmd generate generate because a standalone workload expects a root command and not a subcommand)
We should be able to add a StandaloneWorkload to an existing operator without requiring that it exists on its own.
Situation:
operator-builder create api
command to add the standalone workloadinit
, it errors outcompanionCliRootcmd
match the existing command with work, but the pathing is wonky (mycmd generate generate
because a standalone workload expects a root command and not a subcommand)We should be able to add a StandaloneWorkload to an existing operator without requiring that it exists on its own.