Rename stack for better project conformance

NASA-IMPACT · Oct 31, 2024 · 407adf7 · 407adf7
1 parent ec74edb
commit 407adf7
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/.github/workflows/deploy.yaml b/.github/workflows/deploy.yaml
@@ -57,7 +57,7 @@ jobs:
       - name: Get ConfigLambdaArn from CloudFormation
         id: get-lambda-arn
         run: |
-          echo "CONFIG_LAMBDA_ARN=$(jq -r '."VedaKeycloakStack-${{ vars.STAGE }}".ConfigLambdaArn' outputs.json)" >> $GITHUB_ENV
+          echo "CONFIG_LAMBDA_ARN=$(jq -r '."veda-keycloak-${{ vars.STAGE }}".ConfigLambdaArn' outputs.json)" >> $GITHUB_ENV
 
       - name: Run Apply Config
         run: npm run apply-config $CONFIG_LAMBDA_ARN
diff --git a/deploy/app.ts b/deploy/app.ts
@@ -42,7 +42,7 @@ privateOauthClients.length
   : console.warn(`No client IDs found in ${CONFIG_DIR}`);
 
 const app = new cdk.App();
-new KeycloakStack(app, `VedaKeycloakStack-${STAGE}`, {
+new KeycloakStack(app, `veda-keycloak-${STAGE}`, {
   /* If you don't specify 'env', this stack will be environment-agnostic.
    * Account/Region-dependent features and context lookups will not work,
    * but a single synthesized template can be deployed anywhere. */