Try CF invalidation

Author: Scanz25

bitbucket-pipelines.yml

@@ -218,11 +218,13 @@ definitions:
         name: Find and Invalidate CloudFront Cache
         image: amazon/aws-cli
         script:
-          - aws configure set aws_access_key_id $AWS_ACCESS_KEY_ID
-          - aws configure set aws_secret_access_key $AWS_SECRET_ACCESS_KEY
+          - aws configure set aws_access_key_id $AWS_ACCESS_CF_KEY_ID
+          - aws configure set aws_secret_access_key $AWS_SECRET_ACCESS_CF_KEY
           - aws configure set default.region $AWS_REGION
           - export CLOUDFRONT_NAME=$(echo "$BITBUCKET_BRANCH" | awk -F'/' '{if(NF==1)val=$1;else if(NF==2)val=$2;else if(NF==3)val=$2;else val=$3;gsub(/_/, "-", val);print tolower(val)}')
+          - echo $CLOUDFRONT_NAME
           - export CLOUDFRONT_DISTRIBUTION_ID=$(aws cloudfront list-distributions --query "DistributionList.Items[?Comment=='dev--$CLOUDFRONT_NAME'].Id" --output text)
+          - echo $CLOUDFRONT_DISTRIBUTION_ID
           - aws cloudfront create-invalidation --distribution-id $CLOUDFRONT_DISTRIBUTION_ID --paths "/*"
 
     - step: &find-and-invalidate-cloudfront-staging
@@ -253,6 +255,8 @@ pipelines:
       - step: *turn-on-dev
     turn-on-staging:
       - step: *turn-on-staging
+    invalidate-cloudfront-dev:
+      - step: *find-and-invalidate-cloudfront-dev
   branches:
     'dspace-cris-2024_02_x':
       - step: *preliminary-operation