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 crossplane dependencies #41

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

chore(deps): update crossplane dependencies #41

wants to merge 1 commit into from
+2 −2

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 28, 2024

This PR contains the following updates:

Package Update Change
crossplane-contrib/function-patch-and-transform minor v0.4.0 -> v0.7.0
upbound/provider-gcp minor v1.0.1 -> v1.10.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

crossplane-contrib/function-patch-and-transform (crossplane-contrib/function-patch-and-transform)

v0.7.0

Compare Source

What's Changed

New Contributors

Full Changelog: crossplane-contrib/function-patch-and-transform@v0.6.0...v0.7.0

v0.6.0

Compare Source

What's Changed

New Contributors

Full Changelog: crossplane-contrib/function-patch-and-transform@v0.5.0...v0.6.0

v0.5.0

Compare Source

Notable Changes

What's Changed

New Contributors

Full Changelog: crossplane-contrib/function-patch-and-transform@v0.4.0...v0.5.0

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

v1.10.0

Compare Source

The v1.10.0 release introduces the following new resources.

  • ResponsePolicy.dns.gcp.upbound.io/v1beta1
  • ResponsePolicyRule.dns.gcp.upbound.io/v1beta1
  • TrustConfig.certificatemanager.gcp.upbound.io/v1beta1

What's Changed

Full Changelog: crossplane-contrib/provider-upjet-gcp@v1.9.0...v1.10.0

v1.9.0

Compare Source

The v1.9.0 release introduces the Terraform provider upgrade from 5.39.0 to 5.44.2, new resources, bug fixes, enhancements, and dependency updates.

Support for New Resources
  • ServiceConnectionPolicy.networkconnectivity.gcp.upbound.io/v1beta1
  • Cluster.redis.gcp.upbound.io/v1beta1
  • PolicyTag.datacatalog.gcp.upbound.io/v1beta1
  • Taxonomy.datacatalog.gcp.upbound.io/v1beta1

What's Changed

New Contributors

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

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

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • 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 requested a review from a team as a code owner November 28, 2024 22:55
@renovate renovate bot added the automated label Nov 28, 2024
@village-labs-bot Village Labs Bot
Copy link

upbound/configuration-gcp-network #41

Change Summary

  • Version upgrade of provider-gcp-compute dependency from v1.0.1 to v1.10.0
  • Version upgrade of function-patch-and-transform dependency from v0.4.0 to v0.7.0

Potential Vulnerabilities

  • File: crossplane.yaml:14-15
  • Code: version: "v1.10.0"
  • Explanation: Major version jump from v1.0.1 to v1.10.0 could introduce breaking changes in the provider API that might expose new security configurations or default behaviors that need to be verified.

Code Smells

None identified in this change.

Debug Logs

None identified in this change.

Unintended Consequences

  1. Provider Version Jump:

    • File: crossplane.yaml:14-15
    • Code: version: "v1.10.0"
    • Explanation: The significant version increase (v1.0.1 to v1.10.0) spans multiple releases and could introduce breaking changes in resource handling, configuration formats, or API behaviors that might affect existing infrastructure.

  2. Function Version Jump:

    • File: crossplane.yaml:17
    • Code: version: "v0.7.0"
    • Explanation: The upgrade from v0.4.0 to v0.7.0 of the patch-and-transform function could alter how existing patches and transformations are processed, potentially affecting resource configurations.

Risk Score: 7

The high risk score is primarily due to the significant version jumps in both dependencies, which could potentially impact existing infrastructure and resource management. The change from v1.0.1 to v1.10.0 in the provider is particularly concerning as it represents a major leap in versions that could introduce breaking changes.

@kaessert
Copy link
Contributor

/test-examples

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
@kaessert