Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
Bug Fix: Correct error type parsing for restJson services.
Announcement: When receiving an error response in restJson-based services, an incorrect error type may have been returned based on the content of the response. This has been fixed via PR #2012 tracked in issue #1910.
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 ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
- `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
- `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency
- `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
Bumps the aws-sdk-go group with 5 updates in the / directory:
1.27.33
1.27.35
1.34.9
1.34.10
1.35.2
1.35.3
1.61.2
1.61.3
1.34.8
1.34.9
Bumps the aws-sdk-go group with 5 updates in the /v2/awsv1shim directory:
1.27.33
1.27.35
1.34.9
1.34.10
1.35.2
1.35.3
1.61.2
1.61.3
1.34.8
1.34.9
Updates
github.com/aws/aws-sdk-go-v2/config
from 1.27.33 to 1.27.35Commits
13c3784
Release 2024-09-170097c82
Regenerated Clients590384d
Update API model6a28d22
BREAKFIX: Only generate AccountIDEndpointMode config for services that use it...0d08ea0
Release 2024-09-1683c15f1
Regenerated Clients093ffb6
Update endpoints modele43f191
Update API model1282c53
ReadAWS_CONTAINER_CREDENTIALS_FULL_URI
env variable if set when reading a ...171151b
Release 2024-09-13Updates
github.com/aws/aws-sdk-go-v2/credentials
from 1.17.32 to 1.17.33Commits
13c3784
Release 2024-09-170097c82
Regenerated Clients590384d
Update API model6a28d22
BREAKFIX: Only generate AccountIDEndpointMode config for services that use it...0d08ea0
Release 2024-09-1683c15f1
Regenerated Clients093ffb6
Update endpoints modele43f191
Update API model1282c53
ReadAWS_CONTAINER_CREDENTIALS_FULL_URI
env variable if set when reading a ...171151b
Release 2024-09-13Updates
github.com/aws/aws-sdk-go-v2/service/dynamodb
from 1.34.9 to 1.34.10Commits
Updates
github.com/aws/aws-sdk-go-v2/service/iam
from 1.35.2 to 1.35.3Changelog
Sourced from github.com/aws/aws-sdk-go-v2/service/iam's changelog.
... (truncated)
Commits
ac28b42
Release 2023-02-156da6aab
Regenerated Clients106a028
Update endpoints model6795d67
Update API model1f9c50e
bugfix: correct error type parsing for restJson services04aa6ff
Release 2023-02-14e102656
Regenerated Clients2851996
Update API model1dcf243
Fix v4a tests broken in Go 1.20 (#2017)81ac480
regenerateUpdates
github.com/aws/aws-sdk-go-v2/service/s3
from 1.61.2 to 1.61.3Commits
13c3784
Release 2024-09-170097c82
Regenerated Clients590384d
Update API model6a28d22
BREAKFIX: Only generate AccountIDEndpointMode config for services that use it...0d08ea0
Release 2024-09-1683c15f1
Regenerated Clients093ffb6
Update endpoints modele43f191
Update API model1282c53
ReadAWS_CONTAINER_CREDENTIALS_FULL_URI
env variable if set when reading a ...171151b
Release 2024-09-13Updates
github.com/aws/aws-sdk-go-v2/service/sqs
from 1.34.8 to 1.34.9Commits
13c3784
Release 2024-09-170097c82
Regenerated Clients590384d
Update API model6a28d22
BREAKFIX: Only generate AccountIDEndpointMode config for services that use it...0d08ea0
Release 2024-09-1683c15f1
Regenerated Clients093ffb6
Update endpoints modele43f191
Update API model1282c53
ReadAWS_CONTAINER_CREDENTIALS_FULL_URI
env variable if set when reading a ...171151b
Release 2024-09-13Updates
github.com/aws/aws-sdk-go-v2/service/sso
from 1.22.7 to 1.22.8Commits
8abec4c
Release 2024-05-2370e7095
Regenerated Clients0b2a340
Update partitions filec1eb2d9
Update endpoints model4c990d1
Update API modelc6c1626
s3: handle unrecognized values for Expires in responses (#2653)8209abb
Release 2024-05-2281ad168
Regenerated Clients5c92ae7
Update endpoints model6eeecd9
Update API modelUpdates
github.com/aws/aws-sdk-go-v2/service/sts
from 1.30.7 to 1.30.8Commits
Updates
github.com/aws/aws-sdk-go-v2/config
from 1.27.33 to 1.27.35Commits
13c3784
Release 2024-09-170097c82
Regenerated Clients590384d
Update API model6a28d22
BREAKFIX: Only generate AccountIDEndpointMode config for services that use it...0d08ea0
Release 2024-09-1683c15f1
Regenerated Clients093ffb6
Update endpoints modele43f191
Update API model1282c53
ReadAWS_CONTAINER_CREDENTIALS_FULL_URI
env variable if set when reading a ...171151b
Release 2024-09-13Updates
github.com/aws/aws-sdk-go-v2/credentials
from 1.17.32 to 1.17.33Commits
13c3784
Release 2024-09-170097c82
Regenerated Clients590384d
Update API model6a28d22
BREAKFIX: Only generate AccountIDEndpointMode config for services that use it...0d08ea0
Release 2024-09-1683c15f1
Regenerated Clients093ffb6
Update endpoints modele43f191
Update API model1282c53
ReadAWS_CONTAINER_CREDENTIALS_FULL_URI
env variable if set when reading a ...171151b
Release 2024-09-13Updates
github.com/aws/aws-sdk-go-v2/service/dynamodb
from 1.34.9 to 1.34.10Commits
Updates
github.com/aws/aws-sdk-go-v2/service/iam
from 1.35.2 to 1.35.3Changelog
Sourced from github.com/aws/aws-sdk-go-v2/service/iam's changelog.
... (truncated)
Commits
ac28b42
Release 2023-02-156da6aab
Regenerated Clients106a028
Update endpoints model6795d67
Update API model1f9c50e
bugfix: correct error type parsing for restJson services04aa6ff
Release 2023-02-14e102656
Regenerated Clients2851996
Update API model1dcf243
Fix v4a tests broken in Go 1.20 (#2017)81ac480
regenerateUpdates
github.com/aws/aws-sdk-go-v2/service/s3
from 1.61.2 to 1.61.3Commits
13c3784
Release 2024-09-170097c82
Regenerated Clients590384d
Update API model6a28d22
BREAKFIX: Only generate AccountIDEndpointMode config for services that use it...0d08ea0
Release 2024-09-1683c15f1
Regenerated Clients093ffb6
Update endpoints modele43f191
Update API model1282c53
ReadAWS_CONTAINER_CREDENTIALS_FULL_URI
env variable if set when reading a ...171151b
Release 2024-09-13Updates
github.com/aws/aws-sdk-go-v2/service/sqs
from 1.34.8 to 1.34.9Commits
13c3784
Release 2024-09-170097c82
Regenerated Clients590384d
Update API model6a28d22
BREAKFIX: Only generate AccountIDEndpointMode config for services that use it...0d08ea0
Release 2024-09-1683c15f1
Regenerated Clients093ffb6
Update endpoints modele43f191
Update API model1282c53
ReadAWS_CONTAINER_CREDENTIALS_FULL_URI
env variable if set when reading a ...171151b
Release 2024-09-13Updates
github.com/aws/aws-sdk-go-v2/service/sso
from 1.22.7 to 1.22.8Commits
8abec4c
Release 2024-05-2370e7095
Regenerated Clients0b2a340
Update partitions filec1eb2d9
Update endpoints model4c990d1
Update API modelc6c1626
s3: handle unrecognized values for Expires in responses (#2653)8209abb
Release 2024-05-2281ad168
Regenerated Clients5c92ae7
Update endpoints model6eeecd9
Update API modelUpdates
github.com/aws/aws-sdk-go-v2/service/sts
from 1.30.7 to 1.30.8Commits
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