Investigate what type of cli will address the complexity of the carvel tools

[aaronshurley]

Given the feedback that using the three tools (ytt, kbld, kapp) complicates the workflows for operators that are new to the toolset, we should investigate if we should introduce a cli that combines these tools so the user has the option to avoid interacting with the building blocks but can still interact with the three separate clis if they want

[pivotaljohn]

Ask me about @paulczar's idea: cvl.

[microwavables]

moved from /carvel-community to /carvel as we are merging the two into one

[vrabbi]

Is this still being planned? I think maybe something like the tanzu cli for tkg or even kubectl, having a plugin based cli would be awesome. Makes managing the different tools and feature subsets easier for new users.

[cppforlife]

Is this still being planned?

nothing concrete is currently planned (this issue was made to record an idea).

Makes managing the different tools and feature subsets easier for new users.

im curious about your perspective on this. are you talking about installation of tools, and if so shouldnt existing package managers like brew (on os x for example) cover this case extensively?

[vrabbi]

The installation is less what im getting at. More so the notion of when its a single cli woth subcommands it is more welcoming in my opinion and makea it more understandable that this is a full solution and not just a set of tools while still allowing for use of any of the tools seperately. Also using the plugin method, you can easily upgrade any of the plugins without need to upgrade them all similar to the current behavior whem they are seperate cli tools.
I believe that sometimes a wrapper cli like the tanzu cli can simply make the ux for newcommers a bit more friendly