AM-5152: Update confluent rbac role list
integration test format to reflect a real API call
#3020
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release Notes
This PR will not introduce any changes to a user of the Confluent CLI. This only updates one of our integration tests.
Checklist
What
section below whether this PR applies to Confluent Cloud, Confluent Platform, or both.Test & Review
section below.Blast Radius
section below.What
The
confluent rbac role list
test was improperly formatted. This test was setup in a way to call multiple namespaces containing different roles in a single test. Over time, this test degraded and was setup to call the same namespace multiple times, resulting in the test showing a duplicated list of roles. This initial testing strategy came from a concept that customers could query our list endpoint for different role namespaces. The two issues with this are:This test should not have a comprehensive list of all production roles, as that wouldn't really be testing anything of value and would require constant updates. Instead, this test has been modified to only return a few of our roles in a single namespace, which allows us to ensure the formatting of the output is correct, which is all we can gain from this test anyways.
Blast Radius
There is no end-user blast radius associated with this change, as it only touches an integration test and no public feature.
References
Previous CLI list update PR
AM-5152
Test & Review
The rbac cloud-list tests were updated to demonstrate these changes in behavior.