Bump hashicorp/google from 5.40.0 to 5.41.0

[dependabot]

Bumps hashicorp/google from 5.40.0 to 5.41.0.

Release notes

Sourced from hashicorp/google's releases.

v5.41.0

DEPRECATIONS:

• resourcemanager: deprecated skip_delete field in the google_project resource. Use deletion_policy instead. (#18867)

FEATURES:

• New Data Source: google_logging_log_view_iam_policy (#18990)
• New Data Source: google_scc_v2_organization_source_iam_policy (#19004)
• New Resource: google_access_context_manager_service_perimeter_dry_run_egress_policy (#18994)
• New Resource: google_access_context_manager_service_perimeter_dry_run_ingress_policy (#18994)
• New Resource: google_scc_v2_folder_mute_config (#18924)
• New Resource: google_scc_v2_project_mute_config (#18993)
• New Resource: google_scc_v2_project_notification_config (#19008)
• New Resource: google_scc_v2_organization_source (#19004)
• New Resource: google_scc_v2_organization_source_iam_binding (#19004)
• New Resource: google_scc_v2_organization_source_iam_member (#19004)
• New Resource: google_scc_v2_organization_source_iam_policy (#19004)
• New Resource: google_logging_log_view_iam_binding (#18990)
• New Resource: google_logging_log_view_iam_member (#18990)
• New Resource: google_logging_log_view_iam_policy (#18990)

IMPROVEMENTS:

• clouddeploy: added gke.proxy_url field to google_clouddeploy_target (#19016)
• cloudrunv2: added field binary_authorization.policy to resource google_cloud_run_v2_job and resource google_cloud_run_v2_service to support named binary authorization policy. (#18995)
• compute: added source_regions field to google_compute_healthcheck resource (#19006)
• compute: added update-in-place support for the google_compute_target_https_proxy.server_tls_policy field (#18996)
• compute: added update-in-place support for the google_compute_region_target_https_proxy.server_tls_policy field (#19007)
• container: added auto_provisioning_locations field to google_container_cluster (#18928)
• dataform: added kms_key_name field to google_dataform_repository resource (#18947)
• discoveryengine: added skip_default_schema_creation field to google_discovery_engine_data_store resource (#19017)
• gkehub: added configmanagement.management and configmanagement.config_sync.enabled fields to google_gkehub_feature_membership (#19016)
• gkehub: added management field to google_gke_hub_feature.fleet_default_member_config.configmanagement (#18963)
• resourcemanager: added deletion_policy field to the google_project resource. Setting deletion_policy to PREVENT will protect the project against any destroy actions caused by a terraform apply or terraform destroy. Setting deletion_policy to ABANDON allows the resource to be abandoned rather than deleted and it behaves the same with skip_delete = true. Default value is DELETE. skip_delete = true takes precedence over deletion_policy = "DELETE".
• storage: added force_destroy field to google_storage_managed_folder resource (#18973)
• storage: added generation field to google_storage_bucket_object resource (#18971)

BUG FIXES:

• compute: fixed google_compute_instance.alias_ip_range update behavior to avoid temporarily deleting unchanged alias IP ranges (#19015)
• compute: fixed the bug that creation of PSC forwarding rules fails in google_compute_forwarding_rule resource when provider default labels are set (#18984)
• sql: fixed a perma-diff in settings.insights_config in google_sql_database_instance (#18962)

Changelog

Sourced from hashicorp/google's changelog.

5.41.0 (August 13, 2024)

DEPRECATIONS:

• resourcemanager: deprecated skip_delete field in the google_project resource. Use deletion_policy instead. (#18867)

FEATURES:

• New Data Source: google_logging_log_view_iam_policy (#18990)
• New Data Source: google_scc_v2_organization_source_iam_policy (#19004)
• New Resource: google_access_context_manager_service_perimeter_dry_run_egress_policy (#18994)
• New Resource: google_access_context_manager_service_perimeter_dry_run_ingress_policy (#18994)
• New Resource: google_scc_v2_folder_mute_config (#18924)
• New Resource: google_scc_v2_project_mute_config (#18993)
• New Resource: google_scc_v2_project_notification_config (#19008)
• New Resource: google_scc_v2_organization_source (#19004)
• New Resource: google_scc_v2_organization_source_iam_binding (#19004)
• New Resource: google_scc_v2_organization_source_iam_member (#19004)
• New Resource: google_scc_v2_organization_source_iam_policy (#19004)
• New Resource: google_logging_log_view_iam_binding (#18990)
• New Resource: google_logging_log_view_iam_member (#18990)
• New Resource: google_logging_log_view_iam_policy (#18990)

IMPROVEMENTS:

• clouddeploy: added gke.proxy_url field to google_clouddeploy_target (#19016)
• cloudrunv2: added field binary_authorization.policy to resource google_cloud_run_v2_job and resource google_cloud_run_v2_service to support named binary authorization policy. (#18995)
• compute: added source_regions field to google_compute_healthcheck resource (#19006)
• compute: added update-in-place support for the google_compute_target_https_proxy.server_tls_policy field (#18996)
• compute: added update-in-place support for the google_compute_region_target_https_proxy.server_tls_policy field (#19007)
• container: added auto_provisioning_locations field to google_container_cluster (#18928)
• dataform: added kms_key_name field to google_dataform_repository resource (#18947)
• discoveryengine: added skip_default_schema_creation field to google_discovery_engine_data_store resource (#19017)
• gkehub: added configmanagement.management and configmanagement.config_sync.enabled fields to google_gkehub_feature_membership (#19016)
• gkehub: added management field to google_gke_hub_feature.fleet_default_member_config.configmanagement (#18963)
• resourcemanager: added deletion_policy field to the google_project resource. Setting deletion_policy to PREVENT will protect the project against any destroy actions caused by a terraform apply or terraform destroy. Setting deletion_policy to ABANDON allows the resource to be abandoned rather than deleted and it behaves the same with skip_delete = true. Default value is DELETE. skip_delete = true takes precedence over deletion_policy = "DELETE".
• storage: added force_destroy field to google_storage_managed_folder resource (#18973)
• storage: added generation field to google_storage_bucket_object resource (#18971)

BUG FIXES:

• compute: fixed google_compute_instance.alias_ip_range update behavior to avoid temporarily deleting unchanged alias IP ranges (#19015)
• compute: fixed the bug that creation of PSC forwarding rules fails in google_compute_forwarding_rule resource when provider default labels are set (#18984)
• sql: fixed a perma-diff in settings.insights_config in google_sql_database_instance (#18962)

Commits

• 6523d84 Revert "feat: support Cloud SQL's new field server_ca_mode. (#11331) (#18998)...
• f2b6407 Update CHANGELOG.md for 5.41.0 (#19046)
• f6d7369 Revert "Add send_age_if_zero field and deprecate no_age. (#11098)" (#11404) (...
• 372cf87 Update deprecation message for google_project.skip_delete (#11397) (#19042)
• 9995c48 Add deletion_policy field to Project resource (#11359) (#19026)
• 9af2f7e Skip default schema while datastore creation (#11311) (#19017)
• cff46d6 update dcl to 1.70 (#11285) (#19016)
• 541d33b Add retaining unchanged alias ip ranges and handle permadiff caused by the ch...
• 5ab7d44 Made managed zone test use a random test prefix (#11375) (#19013)
• cada5b3 Sync version_6_upgrade.html.markdown (#11379) (#19012)
• Additional commits viewable 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 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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by CodeRabbit

• New Features

  • Updated the Google Cloud provider version to enhance functionality with potential new features and improvements.

• Security

  • Enhanced security and reliability by updating the integrity verification hashes for the Google provider, ensuring the deployment environment's safety.

[coderabbitai]

Warning

Rate limit exceeded

@dependabot[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 25 minutes and 53 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between c46133c and 6c76c1f.

Walkthrough

The recent changes reflect a minor but significant update to the Google provider within a Terraform configuration. By incrementing the version from 5.40.0 to 5.41.0, this update enhances the provider's functionality, likely bringing new features, improvements, or bug fixes. Additionally, the complete replacement of the associated hash values indicates a rigorous verification of the provider's integrity, which is crucial for maintaining the reliability of the deployment process with Google services.

Changes

Files	Change Summary
.terraform.lock.hcl	Updated Google provider version from 5.40.0 to 5.41.0; hashes replaced for integrity verification.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.