We use the aws-s3-deploy pipe with the following configuration to upload files from the repository to s3.
- pipe: atlassian/aws-s3-deploy:0.2.1
Even though no of the files in `resources` has changed, the entire folder is uploaded on each deployment.
The files in the given local path are commited in the repository and should also not be affected by any other steps in the deployment.
Hi @Nicolas . The pipe users the s3 sync CLI under the hood, so it's a bit tricky to sync only changed files. One possible solution might be to use the combination of --exclude/--include options (see the sync command reference for details). You can pass them via the EXTRA_ARGS pipe variable. Basically, you could get the list of changed files from git and include these files and exclude files that were unchanged.
@Nicolas you could also try to add --size-only to the EXTRA_ARGS pipe variable. This will tell the aws s3 sync to only upload files that have changed the size. See https://docs.aws.amazon.com/cli/latest/reference/s3/sync.html for how this option affects the sync command behavior.
Hi All! We’re excited to share the launch of an announcement banner that lets Jira site administrators communicate directly to their users across their Jira Cloud instance. ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events