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

chore(deps): update dependency upbound/provider-gcp to v1 #27

Merged
merged 3 commits into from
Mar 11, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 8, 2024

Mend Renovate

This PR contains the following updates:

Package Update Change
upbound/provider-gcp major v0.41.1 -> v1.0.0

Release Notes

upbound/provider-gcp (upbound/provider-gcp)

v1.0.0

Compare Source

In the v1.0.0 release, we've upgraded the underlying Terraform provider version from 4.77.0 to 5.19.0.
Explore the API Changes section below for a concise overview of the modifications introduced by this version bump.

The release introduces support for the conversion functions to be able to handle any future breaking API changes. Also includes updates to the dependencies.

With this release, the provider-gcp-cloudiot family provider has been removed with the following two resources:

  • Device.cloudiot.gcp.upbound.io/v1beta1
  • Registry.cloudiot.gcp.upbound.io/v1beta1
Bug Fixes and Enhancements
API Changes
  • Changed external name configuration for Membership.gkehub.gcp.upbound.io/v1beta1 and DNSAuthorization.certificatemanager.gcp.upbound.io/v1beta1, and spec.forProvider.location is now required.
  • Instance.alloydb.gcp.upbound.io/v1beta1 => added reference and selector for spec.forProvider.instanceType field.
  • Routine.bigquery.gcp.upbound.io/v1beta1 => spec.forProvider.routineType is now required.
  • Function.cloudfunctions2.gcp.upbound.io/v1beta1 => spec.forProvider.location is now required.
  • DomainMapping.cloudrun.gcp.upbound.io/v1beta1 => spec.forProvider.metadata is now optional.
  • V2Job.cloudrun.gcp.upbound.io/v1beta1 => spec.forProvider.location is now required and spec.forProvider.template.template.containers.{livenessProbe,startupProbe} have been removed.
  • Service.cloudrun.gcp.upbound.io/v1beta1 => spec.forProvider.location is now required.
  • NodeGroup.compute.gcp.upbound.io/v1beta1 => spec.forProvider.size has been replaced with spec.forProvider.initialSize.
  • RouterNAT.compute.gcp.upbound.io/v1beta1 => spec.forProvider.natIpAllocateOption is now optional.
  • Cluster.container.gcp.upbound.io/v1beta1 => spec.forProvider.enableBinaryAuthorization has been removed.
  • Trigger.eventarc.gcp.upbound.io/v1beta1 => spec.forProvider.destination.cloudFunction has been removed.
  • Certificate.privateca.gcp.upbound.io/v1beta1 => status.atProvider.pemCertificates has been removed and status.atProvider.certificateDescription.configValues has been removed.
  • Secret.secretmanager.gcp.upbound.io/v1beta1 => spec.forProvider.replication.automatic has been replaced with spec.forProvider.replication.auto.
  • Databaselnstance.sql.gcp.upbound.io/v1beta1 => status.atProvider.serverCaCert has been removed.
  • SSLCert.sql.gcp.upbound.io/v1beta1 => status.atProvider.serverCaCert has been removed.
What's Changed
New Contributors

Full Changelog: crossplane-contrib/provider-upjet-gcp@v0.41.2...v1.0.0

v0.41.2

Compare Source

The release v0.41.2 includes some important bug fixes and dependency bumps detailed below:

  • Bump crossplane-runtime to v1.15.1 along with various bug fixes.
  • Bump upjet to v1.1.1
  • There’s a fix in the implementation of the LateInitialize management policy in the context of the no-fork architecture. Previously, we were relying solely on the managed reconciler for preventing the late-initialization of the managed resources if the specified policies do not contain it. Now, we also explicitly skip the late-initialization in upjet to prevent some accidental updates to the spec.forProvider while, for example, updating the annotations.
  • Adds a more explanatory error message when immutable fields of a managed resource have changed.
What's Changed

Full Changelog: crossplane-contrib/provider-upjet-gcp@v0.41.1...v0.41.2


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the automated label Mar 8, 2024
@haarchri haarchri force-pushed the renovate/upbound-provider-gcp-1.x branch from cef8fc4 to 2826635 Compare March 8, 2024 14:13
@haarchri
Copy link
Member

haarchri commented Mar 8, 2024

/test-examples

Copy link
Contributor Author

renovate bot commented Mar 8, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

@haarchri
Copy link
Member

/test-examples

@@ -125,6 +125,7 @@ spec:
kind: Cluster
spec:
forProvider:
deletionProtection: false
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

since tf provider 5.x
image

@haarchri
Copy link
Member

/test-examples

@haarchri haarchri merged commit b3e21f9 into main Mar 11, 2024
2 checks passed
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.

1 participant