Bump einaregilsson/beanstalk-deploy from 14 to 22

[dependabot]

Bumps einaregilsson/beanstalk-deploy from 14 to 22.

Release notes

Sourced from einaregilsson/beanstalk-deploy's releases.

v22

What's Changed

• Make maximum exponential back-off retries configurable by @​n-hebert in einaregilsson/beanstalk-deploy#96
• Upgrade to node 20 by @​davecarlson in einaregilsson/beanstalk-deploy#106

New Contributors

• @​davecarlson made their first contribution in einaregilsson/beanstalk-deploy#106

Full Changelog: einaregilsson/beanstalk-deploy@v21...v22

v21 - Use node16 runner

What's Changed

• Use node16 -- GH actions has deprecated 12 by @​keevie in einaregilsson/beanstalk-deploy#92
• Update README by @​gzur in einaregilsson/beanstalk-deploy#94

New Contributors

• @​keevie made their first contribution in einaregilsson/beanstalk-deploy#92
• @​gzur made their first contribution in einaregilsson/beanstalk-deploy#94

Full Changelog: einaregilsson/beanstalk-deploy@v20...v21

Retry throttled API requests for all operations

Changed the AWS logic so now all operations will retry with exponential back-off when they are throttled by AWS. Max 10 retry attempts for every operation, the retry attempts will be logged as warnings in the build log.

Thanks to @​n-hebert for his contributions.

Allow upload only actions to result in no change when version already exists.

When you use the action without an environment name then it only creates a new version in Beanstalk but doesn't deploy it anywhere. This can for example be used if you want to first just upload a version, then run the action again to deploy to many environments in a matrix action. If a workflow run fails somewhere after you've uploaded the version you might want to run it again. In that case it can be useful to run an upload only action that checks if a version already exists in Beanstalk and does nothing if the version exists.

This can now be done by setting the use_existing_version_if_available parameter to true. When it's set to true and no environment name is set then the action will check if the version exists and exit successfully if it exists. If it doesn't exist the action uploads the version.

Thanks to @​n-hebert for the pull-request.

Use existing bucket option

One new feature in this release, the ability to use an existing bucket for your builds, not the one EB creates for you. Use the optional existing_bucket_name parameter to specify a bucket. Thanks to @​dsiemensma-m4m who contributed this change.

Use region specific buckets

This release fixes an issue with buckets in regions other than the default region. No change is needed to the parameters, it should just work now.

Fix encoding of version label and description

Two changes in this release:

1. A lot of special character errors were happening because a lot of characters are illegal in S3 filenames but are legal in the version label itself in Elastic Beanstalk. So now we replace any characters other than letters, numbers and - and _ with a dash, - in the S3 filename, but leave the version label as it is. The only character that Elastic Beanstalk itself has a problem with in a version label is the forward slash /, so you still can't use that one.

2. Many people like to use their latest commit message ${{github.event.head_commit.message}} as the version description but were having problems. The action will now truncate the message at 200 characters, so it doesn't cause Elastic Beanstalk to reject it. It's now also encoding asterisk * correctly, which was causing a lot of squash commits to fail.

Allow more special characters in version label

One change in this release. A lot of special character errors were happening because a lot of characters are illegal in S3 filenames but are legal in the version label itself in Elastic Beanstalk. So now we replace any characters other than letters, numbers and - and _ with a dash, - in the S3 filename, but leave the version label as it is.

... (truncated)

Commits

• 27edd8a Upgrade to node 20 (#106)
• 97974c0 Make maximum exponential back-off retries configurable (#96)
• 18e5b85 Update README (#94)
• 2c184e2 Upgrade to node16 (#92)
• 6f594de Merge pull request #75 from einaregilsson/exponential-backoff
• 7a235e2 Update version to 20
• bc721e1 Use warnings for messages inside aws-api-request.js
• 1176d87 Tidy up lines and remove unused code
• 0df1c96 Test without fail
• e3a852a Fix terrible, no-good very-bad error
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

The following labels could not be found: dependencies.