Open bwaldecker opened 9 months ago
Thanks for the report @bwaldecker we're investigating but to help can you provide the output of tanzu plugin list
?
maybe to highlight: listing and creation on cluster level works as expected
output from "tanzu plugin list"
Standalone Plugins
NAME DESCRIPTION TARGET VERSION STATUS
pinniped-auth Pinniped authentication operations (usually not directly invoked) global v0.31.1 installed
telemetry configure cluster-wide settings for vmware tanzu telemetry global v1.1.0 installed
Plugins from Context: TMC-SaaS
NAME DESCRIPTION TARGET VERSION STATUS
account Account for tmc resources mission-control v0.2.0 installed
agentartifacts helm for tmc resources mission-control v0.1.17 installed
aks-cluster Manage and unmanage tmc aks clusters mission-control v0.3.2 installed
apply Create/Update a resource with a resource file mission-control v0.3.14 installed
audit Run an audit request on an org mission-control v0.1.17 installed
cluster mission-control v0.2.12 installed
clustergroup A group of Kubernetes clusters mission-control v0.1.17 installed
context mission-control v0.1.12 installed
continuousdelivery Continuousdelivery for tmc resources mission-control v0.1.17 installed
data-protection Data protection for tmc resources mission-control v0.1.17 installed
ekscluster mission-control v0.2.2 installed
events Events for any meaningful user activity or system state change mission-control v0.1.17 installed
helm helm for tmc resources mission-control v0.1.18 installed
iam IAM Policies for tmc resources mission-control v0.1.17 installed
inspection Inspection for tmc resources mission-control v0.1.17 installed
integration Get available integrations and their information from registry mission-control v0.1.17 installed
management-cluster A TMC registered Management cluster mission-control v0.2.18 installed
policy Policy for tmc resources mission-control v0.1.17 installed
provider-aks-cluster Manage and unmanage tmc provider aks clusters mission-control v0.1.18 installed
provider-eks-cluster mission-control v0.1.17 installed
secret secret for tmc resources mission-control v0.1.19 installed
setting Setting plugin for tmc resources mission-control v0.2.15 installed
tanzupackage Tanzupackage for TMC resources mission-control v0.4.3 installed
workspace A group of Kubernetes namespaces mission-control v0.1.19 installed
Bug description
It is not possible to list or create an IAM policy
Expected behavior list
Steps to reproduce the bug / Relevant debug output
command: tanzu mission-control iam list --scope cluster-group -n
Output: null
Command: tanzu mission-control iam add-binding --scope cluster-group --role --users --cluster
Command: tanzu mission-control iam add-binding --scope cluster-group --role --users -n
Output: Error: Scope needs to be specified
Output of
tanzu version
version: v1.1.0 buildDate: 2023-11-01 sha: d0679f5a arch: arm64
Environment where the bug was observed (cloud, OS, etc)
TMC SaaS