fix: maximum value for SQS deliveryDelay is 15 minutes, not 15 seconds

[ssemyonov]

Description

According to AWS documentation the maximum amount of delay is 15 minutes and the property is set in seconds, therefore the maximum in the binding needs to be updated accordingly.

[github-actions]

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[Pakisan]

@ssemyonov hi!

Thanks for your contribution. Please move your change from auto generated schema to this schemas:

• https://github.com/asyncapi/spec-json-schemas/blob/master/bindings/sqs/0.2.0/channel.json
• https://github.com/asyncapi/spec-json-schemas/blob/master/bindings/sqs/0.3.0/channel.json

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[fmvilas]

LGTM 👍 Good catch!

[derberg]

@dpwdec please remember next time to merge PRs using our commands, instead of doing it manually in GH. Just add /rtm comment. And don't worry if you can't remember, you can always just drop /help comment if needed.

we added this command automation because like in this PR and others in the past quite often we forget to make sure that commit message follows conventional commits. /rtm command makes sure commit message is the same as PR title.

now, in master we have commit message Fix - SQS deliveryDelay maximum is 15 minutes, not 15 seconds instead of fix: maximum value for SQS deliveryDelay is 15 minutes, not 15 seconds and no release is going to be triggered automatically

[asyncapi-bot]

Hello, @derberg! 👋🏼

    I'm 🧞🧞🧞 Genie 🧞🧞🧞 from the magic lamp. Looks like somebody needs a hand!

    At the moment the following comments are supported in pull requests:

    - `/please-take-a-look` or `/ptal` - This comment will add a comment to the PR asking for attention from the reviewrs who have not reviewed the PR yet.
    - `/ready-to-merge` or `/rtm` - This comment will trigger automerge of PR in case all required checks are green, approvals in place and do-not-merge label is not added
    - `/do-not-merge` or `/dnm` - This comment will block automerging even if all conditions are met and ready-to-merge label is added
    - `/autoupdate` or `/au` - This comment will add `autoupdate` label to the PR and keeps your PR up-to-date to the target branch's future changes. Unless there is a merge conflict or it is a draft PR. (Currently only works for upstream branches.)
    - `/update` or `/u` - This comment will update the PR with the latest changes from the target branch. Unless there is a merge conflict or it is a draft PR. NOTE: this only updates the PR once, so if you need to update again, you need to call the command again.

[dpwdec]

Really sorry @derberg! Is there anything I can do to fix it? Reverting etc. Or can it be fixed forward for releases?
I'll ensure I use the slash commands in future 🙇

[derberg]

no worries, I'm just letting you know for future. Nothing bad happened, unless it is a critical bug that needs to be somewhere fixed quickly 😄

we can revert, we can do dummy empty commit PR - or we can just wait for another PR that would trigger the release

[asyncapi-bot]

🎉 This PR is included in version 6.9.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀