onctl
onctl copied to clipboard
build(deps): bump github.com/Azure/azure-sdk-for-go/sdk/azidentity from 1.7.0 to 1.8.0
Bumps github.com/Azure/azure-sdk-for-go/sdk/azidentity from 1.7.0 to 1.8.0.
Release notes
Sourced from github.com/Azure/azure-sdk-for-go/sdk/azidentity's releases.
sdk/azidentity/v1.8.0
1.8.0 (2024-10-08)
Other Changes
AzurePipelinesCredentialsets an additional OIDC request header so that it receives a 401 instead of a 302 after presenting an invalid system access token- Allow logging of debugging headers for
AzurePipelinesCredentialand include them in error messagessdk/azidentity/v1.8.0-beta.3
1.8.0-beta.3 (2024-09-17)
Features Added
- Added
ObjectIDtype forManagedIdentityCredentialOptions.IDOther Changes
- Removed redundant content from error messages
sdk/azidentity/v1.8.0-beta.2
1.8.0-beta.2 (2024-08-06)
Breaking Changes
NewManagedIdentityCredentialnow returns an error when a user-assigned identity is specified on a platform whose managed identity API doesn't support that.ManagedIdentityCredential.GetToken()formerly logged a warning in these cases. Returning an error instead prevents the credential authenticating an unexpected identity, causing a client to act with unexpected privileges. The affected platforms are:
- Azure Arc
- Azure ML (when a resource ID is specified; client IDs are supported)
- Cloud Shell
- Service Fabric
Other Changes
- If
DefaultAzureCredentialreceives a non-JSON response when probing IMDS before attempting to authenticate a managed identity, it continues to the next credential in the chain instead of immediately returning an error.sdk/azidentity/v1.8.0-beta.1
1.8.0-beta.1 (2024-07-17)
Features Added
- Restored persistent token caching feature
Breaking Changes
These changes affect only code written against a beta version such as v1.7.0-beta.1
- Redesigned the persistent caching API. Encryption is now required in all cases and persistent cache construction is separate from credential construction. The
PersistentUserAuthenticationexample in the package docs has been updated to demonstrate the new API.
... (truncated)
Commits
42def97Add breaking changes to release notes (#21696)112db83Azcore v1.8.0 (#21694)204a3c4Prep azcore v1.7.2 for release (#21506)89497f5Add changelog entry for WASM fix (#21493)0414a4bTransport dialer: setting nil for wasm build (#21451)b1db0beEnable TLS renegotiation (#21182)- See full diff 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 rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency -
@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)