From 5427d01f8fc59d1d095af133cea2cd4c8770c29b Mon Sep 17 00:00:00 2001 From: Gavin Inglis Date: Wed, 10 Jan 2024 01:20:47 +0000 Subject: [PATCH] testsys-launcher(docs): update README to use CFN context the stack switched from using parameterized roles for assuming the testsys-admin role to assuming this role from context. Update the README instructions for deploying to reflect this. Signed-off-by: Gavin Inglis --- deploy/testsys-launcher/README.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/deploy/testsys-launcher/README.md b/deploy/testsys-launcher/README.md index a023c06d..538f31aa 100644 --- a/deploy/testsys-launcher/README.md +++ b/deploy/testsys-launcher/README.md @@ -13,8 +13,9 @@ cdk deploy ``` The default role that can assume the `testsys-admin` role is "Administrator". -During deployment, use `--parameter TestsysAssumerRole={MY-ROLE-NAME}` to specify -a different role that can assume the `testsys-admin` role. +To specify other roles to assume `testsys-admin`, modify `cdk.json` or use +a comma separated set of roles via CDK context like +`--context testsysAdminAssumedBy=,,`. To get the kubeconfig, assuming you are acting as the role that can assume `testsys-admin`, use the `aws eks update-kubeconfig` command with the `testsys-admin` role: @@ -42,5 +43,8 @@ Bottlerocket nodes on the cluster consume the latest releases and stay up to dat ## Optional Parameters -* `TestsysAssumerRole` name of the role that can assume the `testsys-admin` role to perform cluster operations _(string)_ - Default: "Administrator" * `TestsysNodegroupSize` number of instances for the testsys node-group _(number)_ - Default: "3" + +## Optional Context + +* `testsysAdminAssumedBy`: a comma separated list of roles that can assume the `testsys-admin` role - Default: "Administrator"