Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix bug with updating cloudfunctions vpcConnectorEgressSettings #20437

Conversation

modular-magician
Copy link
Collaborator

Addressed a bug with updating vpc_connector_egress_settings field in Cloud Functions. The Cloud Functions v1 API currently requires the vpc_connector field to be set whenever vpc_connector_egress_settings gets updated, even if there are no changes to vpc_connector. This change modifies the resource update to include vpc_connector when vpc_connector_egress_settings is being updated.

Release Note Template for Downstream PRs (will be copied)

cloudfunctions: Fixed issue when updating `vpc_connector_egress_settings` field for `google_cloudfunctions_function` resource.

b/351195255

Derived from GoogleCloudPlatform/magic-modules#12145

…icorp#12145)

[upstream:b1ab6c65474d13c631f7a4b8755e82c82bbbc60c]

Signed-off-by: Modular Magician <magic-modules@google.com>
@modular-magician modular-magician requested a review from a team as a code owner November 21, 2024 22:07
@modular-magician modular-magician merged commit ff576ca into hashicorp:main Nov 21, 2024
4 checks passed
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 23, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant