Skip to content

resourceIdentity: bump sdk/v2 from 0.27.0 -> 0.28.1#15291

Closed
BBBmau wants to merge 1 commit intoGoogleCloudPlatform:FEATURE-BRANCH-resource-identity-generationfrom
BBBmau:bump-sdkv2-latest
Closed

resourceIdentity: bump sdk/v2 from 0.27.0 -> 0.28.1#15291
BBBmau wants to merge 1 commit intoGoogleCloudPlatform:FEATURE-BRANCH-resource-identity-generationfrom
BBBmau:bump-sdkv2-latest

Conversation

@BBBmau
Copy link
Collaborator

@BBBmau BBBmau commented Oct 2, 2025

0.28.1 introduces a fix which was blocking the merging of resource identity due to null attributes being validated on a resource update, this would cause errors for users on AWS when attempting to update a resource with an existing identity.

This will also require us to bump the Golang version from 1.13->1.14 in our CI configurations

Release Note Template for Downstream PRs (will be copied)

See Write release notes for guidance.


@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 33 files changed, 293 insertions(+), 202 deletions(-))
google-beta provider: Diff ( 34 files changed, 293 insertions(+), 196 deletions(-))

Errors

google provider:

  • The diff processor failed to build. This is usually due to the downstream provider failing to compile.

google-beta provider:

  • The diff processor failed to build. This is usually due to the downstream provider failing to compile.

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 0
Passed tests: 0
Skipped tests: 0
Affected tests: 0

Click here to see the affected service packages

All service packages are affected

🔴 Errors occurred during REPLAYING mode. Please fix them to complete your PR.

View the build log

@BBBmau BBBmau closed this Dec 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants