successful package installation is not written to stdout

[JitenPalaparthi]

Bug Report

• Upon successful installation I have received the folling message ""Looking up package to install: gatekeeper.tce.vmware.com:
  Installed package in default/gatekeeper.tce.vmware.com:3.2.3-vmware0"" .
• When I tried to capture the messages to stdout , it has return as empty string to the stdout
• Even upon successful installation of the package , the output is sent to stderr instead of stdout

Expected Behavior

Output should be in stdout not in stderr

Steps to Reproduce the Bug

run the below command
tanzu package install gatekeeper.tce.vmware.com >2&1
From the above command , the stderr output is written to stdout , hence can see the output. Actually the output should be streamed to stdout not to stderr
tanzu package install gatekeeper.tce.vmware.com >>stdouterr.txt
From the about command there is nothing in the file. It should not be the case.

Environment Details

• Build version (tanzu version): version: v1.3.0 | tce: v0.6.0
• Operating System (client): Ubuntu 20.04.2 LTS

[karuppiah7890]

On a parallel note, I would have expected some sort of JSON output flag like --output and -o . Related - #717 , #626

Currently I see -o used for something else

$ tanzu package install -h
Install a package into the cluster

Usage:
  tanzu package install <package name> [flags]

Flags:
  -c, --cluster string           Cluster name which corresponds to a secret
  -g, --config string            Configuration for the package
  -h, --help                     help for install
  -n, --namespace string         Namespace to deploy too (default "default")
  -o, --package-version string   Version of the package
  -p, --paths stringToString     User defined paths for kapp template (default [])
  -u, --url string               URL to image

Also, @JitenPalaparthi , the package plugin (different implementation) is soon going to come from Tanzu Framework repo, but yeah, until then, the package plugin in TCE repo is the one that will be used

[jpmcb]

Thanks for bringing this to our attention!

We are actively working to replace the addon CLI plugin with the Tanzu framework package plugin since addon was just a proof of concept.

That work is being done in #918 and this should be resolved once that replacement has occurred. If not, feel free to open an issue in the tanzu-framework repo!