@@ -31,15 +31,16 @@ Feature: Role CRDs
3131 """
3232 And role "admin-role" is successfully synced
3333 Then role "admin-role" should exist in cluster "roles"
34- And role "admin-role" should have members "alice" and " bob" in cluster "roles"
34+ And role "admin-role" should have members "alice and bob" in cluster "roles"
3535
3636 @skip:gke @skip:aks @skip:eks
3737 Scenario : Manage roles with authorization
3838 Given there is no role "read-only-role" in cluster "roles"
3939 And there are the following pre-existing users in cluster "roles"
4040 | name | password | mechanism |
4141 | charlie | password | SCRAM -SHA -256 |
42- When I apply Kubernetes manifest:
42+ When I create topic "public-test" in cluster "roles"
43+ And I apply Kubernetes manifest:
4344 """
4445# tag::manage-roles-with-authorization[]
4546 # In this example manifest, a role called "read-only-role" is created in a cluster called "roles".
@@ -68,7 +69,7 @@ Feature: Role CRDs
6869 And role "read-only-role" is successfully synced
6970 Then role "read-only-role" should exist in cluster "roles"
7071 And role "read-only-role" should have ACLs for topic pattern "public-" in cluster "roles"
71- And user "charlie" should be able to read from topic "public-test" in cluster "roles"
72+ And "charlie" should be able to read from topic "public-test" in cluster "roles"
7273
7374 @skip:gke @skip:aks @skip:eks
7475 Scenario : Manage authorization-only roles
0 commit comments