Feature Request: AWS Cloudfront Invalidation

[Deleted user]

I just set up s3 deployment and it works great. I was already deploying to s3 from my local machine. However, after deploying, I need to run an AWS Cloudfront invalidation to prevent caching issues. Would it possible to include this in the pipeline?

Specifically what I run locally is:

aws cloudfront create-invalidation --distribution-id XXX --paths /index.html /error.html

[Rudi Starcevic]

Hi @[deleted] 

I was searching for the same solution when google lead me to this thread.

I went ahead and whipped up my own pipe which is working well for me - you may find it useful and are welcome to check it out.

I used the aws-s3-deploy code as a starter and just adapted it.

I use both bitbucket and github, the repo for this pipe is on githhub and published on hub.docker.com

https://github.com/rudijs/aws-cloudfront-create-invalidation

https://cloud.docker.com/repository/docker/rudijs/aws-cloudfront-create-invalidation/

[Murray Rowan]

It seems there is now an official Atlassian way to do so, documented here:

https://jira.atlassian.com/browse/BCLOUD-18563?focusedCommentId=2289580&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-2289580

- pipe: atlassian/aws-cloudfront-invalidate:0.1.2
  variables: 
    AWS_ACCESS_KEY_ID: "<string>"
    AWS_SECRET_ACCESS_KEY: "<string>"
    AWS_DEFAULT_REGION: "<string>"
    DISTRIBUTION_ID: "<string>"
    # PATHS: "<string>" # Optional    # DEBUG: "<boolean>" # Optional

[Ana Retamal]

Hi @[deleted] ,

For feature requests, please use our portal at site/master. That's how we track suggestions from our users and keep a communication between developers, product managers, and users.

Hope that helps,

Ana