Browse Source

test(e2e): give the generator leg aws credentials

The ecr and sts generators mint tokens against real AWS, so the generator leg
needs the aws secret group in addition to grafana. Without it the ecr spec
failed once the leg ran in isolation.

Signed-off-by: Alexander Chernov <alexander@chernov.it>
Alexander Chernov 1 week ago
parent
commit
d0cf825b8a
1 changed files with 3 additions and 4 deletions
  1. 3 4
      e2e/matrix.yaml

+ 3 - 4
e2e/matrix.yaml

@@ -173,14 +173,13 @@ areas:
 
 
   # Non-provider suites. No provider labels, so providers is empty; they run the
   # Non-provider suites. No provider labels, so providers is empty; they run the
   # whole non-managed suite. flux and argocd exercise ESO under GitOps tools and
   # whole non-managed suite. flux and argocd exercise ESO under GitOps tools and
-  # need no creds. generator's grafana specs need the grafana group; the
-  # credential needs of the other generators (e.g. ecr/sts) want a closer look
-  # before this leg is enabled.
+  # need no creds. The generator suite needs grafana (grafana generator) and aws
+  # (the ecr and sts generators mint tokens against real AWS).
   - name: generator
   - name: generator
     suite: generator
     suite: generator
     labels: "!managed"
     labels: "!managed"
     providers: []
     providers: []
-    secret_groups: [grafana]
+    secret_groups: [grafana, aws]
     needs_secrets: true
     needs_secrets: true
     paths:
     paths:
       - "apis/**"
       - "apis/**"