Chandra P

Results 12 issues of Chandra P

### What this PR does / why we need it This PR enhances the plugin installation. After these changes, the plugin installation does not log each successful plugin installation message,...

cla-not-required

### What this PR does / why we need it This PR updates the plugin upload-bundle UX to minimize the log messages while uploading a specific plugin image. It also...

cla-not-required

### What this PR does / why we need it Currently, the CLI build and E2E test cases are being executed only in Ubuntu and MacOS. The goal of this...

cla-not-required

**Describe the feature request** As part of https://github.com/vmware-tanzu/tanzu-cli/pull/483, UX changes have been made to list plugins that are deactivated when 'tanzu context unset' or 'tanzu context delete' is performed. However,...

kind/feature
needs-triage

**Describe the feature request** Currently, the plugin names and plugin group names are hard coded in the end-to-end framework for the plugin life cycle tests, we need to make it...

**Describe the feature request** Currently, we don't have an e2e test cases implementation for the plugin sync (for target Kubernetes) **Describe alternative(s) you've considered** NA **Additional context** NA

kind/testing

**Describe the feature request** Currently, we have E2E test cases for the plugin life cycle, but they are specific to OCI repository; we need to implement plugin life cycle E2E...

(This is used to request new product features) **Describe the feature request** The TKG CLI command `tanzu cluster create clusterName -f config.YAML --dry-run` accepts only legacy config.YAML file only, we...

kind/feature
area/lcm
area/cc
not-core-cli

**Describe the feature request** In TKG CLI, For the cluster class based cluster creation, `tanzu cluster create -f Cluster.yaml`, CLI expects the input file Cluster.yaml has a cluster class based...

area/cli
kind/feature
area/cc
not-core-cli

**Describe the feature request** During cluster creation with CCluster.yaml, the validation of the configuration is done via mapping it back to legacy configuration variables to leverage the existing validation logic....

kind/feature
area/lcm
area/cc
not-core-cli