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.

Sign up for GitHub

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

Jump to bottom

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

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

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 7, 2024 •
edited
Loading

This PR contains the following updates:

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

Release Notes

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

v1.8.3

Compare Source

With the v1.8.3 release we cleaned uptest specific codes/placeholders from the examples in the marketplace.

What's Changed

Full Changelog: crossplane-contrib/provider-upjet-gcp@v1.8.2...v1.8.3

v1.8.2

Compare Source

The v1.8.2 release fixes the issue of hiding error messages.

What's Changed

Full Changelog: crossplane-contrib/provider-upjet-gcp@v1.8.1...v1.8.2

v1.8.1

Compare Source

The v1.8.1 release is reverting this commit, which caused a regression. See related PR https://github.com/crossplane-contrib/provider-upjet-gcp/pull/614

What's Changed

Full Changelog: crossplane-contrib/provider-upjet-gcp@v1.8.0...v1.8.1

v1.8.0

Compare Source

The v1.8.0 release introduces bug fixes, enhancements, and dependency updates.

What's Changed

New Contributors

Full Changelog: crossplane-contrib/provider-upjet-gcp@v1.7.0...v1.8.0

v1.7.0

Compare Source

The v1.7.0 release introduces the Terraform provider upgrade from v5.28.0 to v5.39.0, bug fixes, enhancements, and dependency updates.

What's Changed

New Contributors

Full Changelog: crossplane-contrib/provider-upjet-gcp@v1.6.0...v1.7.0

v1.6.0

Compare Source

The v1.6.0 release introduces new family providers, new resources, an important bug fix, enhancements, and dependency updates.

Support for New Family Providers
  • provider-gcp-orgpolicy
  • provider-gcp-tags
Support for New Resources
  • EnvgroupAttachment.apigee.gcp.upbound.io/v1beta1
  • EndpointAttachment.apigee.gcp.upbound.io/v1beta1
  • InstanceAttachment.apigee.gcp.upbound.io/v1beta1
  • AddonsConfig.apigee.gcp.upbound.io/v1beta1
  • SyncAuthorization.apigee.gcp.upbound.io/v1beta1
  • Policy.orgpolicy.gcp.upbound.io/v1beta1
  • TagBinding.tags.gcp.upbound.io/v1beta1
  • TagKey.tags.gcp.upbound.io/v1beta1
  • TagValue.tags.gcp.upbound.io/v1beta1
Bug Fix

What's Changed

New Contributors

Full Changelog: crossplane-contrib/provider-upjet-gcp@v1.5.0...v1.6.0

v1.5.0

Compare Source

In the release v1.5.0, we've upgraded the underlying Terraform provider version from 5.19.0 to 5.28.0

What's Changed

Full Changelog: crossplane-contrib/provider-upjet-gcp@v1.4.0...v1.5.0

v1.4.0

Compare Source

The v1.4.0 release introduces a new resource named HMACKey.storage.gcp.upbound.io/v1beta1, enhancements, and dependency updates.

What's Changed

New Contributors

Full Changelog: crossplane-contrib/provider-upjet-gcp@v1.3.0...v1.4.0

v1.3.0

Compare Source

The v1.3.0 release introduces bug fixes, documentation updates, and dependency updates.

What's Changed

New Contributors

Full Changelog: crossplane-contrib/provider-upjet-gcp@v1.2.0...v1.3.0

v1.2.0

Compare Source

The v1.2.0 release introduces converting singleton lists in the MR APIs to embedded objects, and dependency updates.

In this release, we've updated how Terraform configuration blocks are handled in our APIs. Terraform configuration blocks, even if they have a MaxItems constraint of 1, are (almost) always generated as lists. We now generate the lists with a MaxItems constraint of 1 as embedded objects in our MR APIs. This also helps when updating or patching via SSA the (previously list) objects.

The new v1beta2 versions of the CRD APIs incorporate these changes, ensuring backward compatibility for clients using the older v1beta1 versions. Any clients wanting to use the embedded objects-based APIs should update to the v1beta2 versions of the CRD APIs.

  • For instance, let's look at the YAML output of the DatabaseInstance.sql.gcp.upbound.io/v1beta2 resource's spec.forProvider, with this release we can see the spec.forProvider.settings field as an object:
spec:
  forProvider:
    databaseVersion: MYSQL_5_7
    deletionProtection: false
    project: official-provider-testing
    region: us-central1
    settings:
      diskSize: 20
      tier: db-f1-micro
  • If we look at the v1beta1 YAML output of the resource, we see the field as a list:
spec:
  forProvider:
    databaseVersion: MYSQL_5_7
    deletionProtection: false
    project: official-provider-testing
    region: us-central1
    settings:
    - diskSize: 20
      tier: db-f1-micro

For a detailed overview of the implementation, please see https://github.com/crossplane/upjet/pull/387 and https://github.com/crossplane/upjet/pull/400

What's Changed

Full Changelog: crossplane-contrib/provider-upjet-gcp@v1.1.0...v1.2.0

v1.1.0

Compare Source

The v1.1.0 release introduces MR metrics, a new family provider provider-gcp-containerattached, new resources, bug fixes, enhancements, and dependency updates.

We are excited to introduce a new set of managed resource (MR) metrics in this release. These metrics are pivotal for monitoring the state and performance of resources managed through Crossplane. This enhancement follows the implementation guidelines from the provider-kubernetes and incorporates changes from https://github.com/crossplane/crossplane-runtime/pull/683. The newly available metrics include:

  • crossplane_managed_resource_exists{"gvk"}
  • crossplane_managed_resource_ready{"gvk"}
  • crossplane_managed_resource_synced{"gvk"}
  • crossplane_managed_resource_first_time_to_reconcile_seconds{"gvk"}
  • crossplane_managed_resource_first_time_to_readiness_seconds{"gvk"}
  • crossplane_managed_resource_deletion_seconds{"gvk"}
  • crossplane_managed_resource_drift_seconds{"gvk"}

For a detailed overview of the implementation, please refer to this https://github.com/crossplane/crossplane-runtime/pull/683.

Note that, for async resources, upjet_resource_ttr_bucket{"group","kind","version"} gives a more accurate measurement of when the external resource becomes available, compared to crossplane_managed_resource_first_time_to_readiness_seconds{"gvk"}.

Support for New Resources
  • RegionNetworkEndpoint.compute.gcp.upbound.io/v1beta1
  • Cluster.containerattached.gcp.upbound.io/v1beta1
Bug Fixes and Enhancements
  • Bug Fix: Addresses a critical bug related to asynchronous operation failures. With this fix, the "Synced" status will immediately reflect as "False" upon any failure in asynchronous operations, ensuring compliance with the XRM contract and improving reliability in status reporting. Previously, the error handling only updated the LastAsyncOperation status without properly setting the Synced condition to False. For more information, please see the https://github.com/crossplane/upjet/pull/391#issue-2262134402.
  • Support for publishing password to Connection Secret for the Uer.sql resource https://github.com/crossplane-contrib/provider-upjet-gcp/pull/501
Breaking UX Changes

The release switches the order of the SYNCED and READY printer columns so that the SYCNED column is now printed before the READY column as follows:

❯ kubectl get managed
NAME                                                                  SYNCED   READY   EXTERNAL-NAME             AGE
serviceaccount.cloudplatform.gcp.upbound.io/example-service-account   True     True    example-service-account   56s

This used to be first the READY column and then the SYNCED column previously. Please see https://github.com/crossplane/upjet/pull/360 for further details.

What's Changed

New Contributors

Full Changelog: crossplane-contrib/provider-upjet-gcp@v1.0.2...v1.1.0

v1.0.2

Compare Source

The release v1.0.2 introduces:

What's Changed

Full Changelog: crossplane-contrib/provider-upjet-gcp@v1.0.1...v1.0.2

v1.0.1

Compare Source

The release v1.0.1 sets a default io.Discard logger for the controller-runtime if debug logging is not enabled. If debug logging is enabled, then the controller-runtime uses a debug mode zap logger as usual.

What's Changed

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

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.
    • spec.forProvider.enableEndpointIndependentMapping now defaults to FALSE. Previously, the default value was TRUE.
  • Cluster.container.gcp.upbound.io/v1beta1 =>
    • spec.forProvider.enableBinaryAuthorization has been removed.
    • spec.forProvider.deletionProtection field has been added with a default of true. Cluster deletion now prevented by default with this field.
    • spec.forProvider.networkingMode defaults to VPC_NATIVE for newly created clusters.
  • 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.
  • ServiceAttachment.compute.gcp.upbound.io/v1beta1 => spec.forProvider.reconcileConnections now defaults from API. Previously defaulted to true.
  • NodePool.container.gcp.upbound.io/v1beta1 => spec.forProvider.autoRepair and spec.forProvider.autoUpgrade now default to true. Previously both fields defaulted to false if spec.forProvider.management was set as an empty block.
  • ProjectSink.logging.gcp.upbound.io/v1beta1 => spec.forProvider.uniqueWriterIdentity now defaults to TRUE. Previously, the default value was FALSE.
What's Changed
New Contributors

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

v0.41.4

Compare Source

The release v0.41.4 introduces:

What's Changed

Full Changelog: crossplane-contrib/provider-upjet-gcp@v0.41.3...v0.41.4

v0.41.3

Compare Source

The release v0.41.3 sets a default io.Discard logger for the controller-runtime if debug logging is not enabled. If debug logging is enabled, then the controller-runtime uses a debug mode zap logger as usual.

What's Changed

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

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the automated label Mar 7, 2024
@renovate renovate bot force-pushed the renovate/upbound-provider-gcp-1.x branch from ffbb130 to c41d82c Compare March 11, 2024 14:59
@haarchri
Copy link
Member

/test-examples

1 similar comment
@haarchri
Copy link
Member

/test-examples

@renovate renovate bot force-pushed the renovate/upbound-provider-gcp-1.x branch 3 times, most recently from 56aa1ca to 5ced0b7 Compare March 16, 2024 11:28
@haarchri
Copy link
Member

/test-examples

@haarchri
Copy link
Member

xref: crossplane-contrib/provider-upjet-gcp#474

@renovate renovate bot force-pushed the renovate/upbound-provider-gcp-1.x branch from 5ced0b7 to b7577cb Compare March 21, 2024 17:44
@renovate renovate bot force-pushed the renovate/upbound-provider-gcp-1.x branch from b7577cb to 6f340d6 Compare April 25, 2024 18:58
@renovate renovate bot force-pushed the renovate/upbound-provider-gcp-1.x branch from 6f340d6 to d7d523e Compare May 16, 2024 23:19
@renovate renovate bot force-pushed the renovate/upbound-provider-gcp-1.x branch from d7d523e to 44a63a9 Compare June 13, 2024 13:40
@renovate renovate bot force-pushed the renovate/upbound-provider-gcp-1.x branch 2 times, most recently from d19a016 to 85e11c2 Compare July 4, 2024 13:29
@renovate renovate bot force-pushed the renovate/upbound-provider-gcp-1.x branch from 85e11c2 to b38cf20 Compare July 26, 2024 14:35
@renovate renovate bot force-pushed the renovate/upbound-provider-gcp-1.x branch from b38cf20 to e357c9c Compare August 6, 2024 17:55
@renovate renovate bot force-pushed the renovate/upbound-provider-gcp-1.x branch from e357c9c to 81f1d1e Compare August 23, 2024 11:42
@renovate renovate bot force-pushed the renovate/upbound-provider-gcp-1.x branch 2 times, most recently from 9c19af4 to aa1b68d Compare September 16, 2024 13:29
@renovate renovate bot force-pushed the renovate/upbound-provider-gcp-1.x branch from aa1b68d to 8cef262 Compare September 20, 2024 22:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
automated
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@haarchri