fix(deps): update module github.com/upbound/upjet to v1 - autoclosed #18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.8.0-rc.0.0.20221024111721-c82119f5ef34
->v1.0.0
Release Notes
upbound/upjet (github.com/upbound/upjet)
v1.0.0
Compare Source
v1.0.0
contains major performance improvements for reconcilingTerraform
resources.
This release introduces two new
managed.Connecter
s and two newmanaged.ExternalClient
s (controller.noForkExternal
and thecontroller.noForkAsyncExternal
) for reconciling Terraformed resources without forking any Terraform CLI or Terraform provider processes.The new external client implementation consumes the Terraform provider's Go provider schema and invokes the CRUD functions registered in that schema via the terraform-plugin-sdk utility functions.
The new external clients employ an in-memory Terraform state cache as these clients no longer construct Terraform workspaces while reconciling their resources.
New external clients provide significant CPU and memory footprint reduction compared to traditional external clients. Below is an example result from Upbound Official
provider-aws
using the new external client for 1K and 10K MR. These results are shared not to provide a Sizing Guide but as a reference to understand the improvements in performance metrics. Also, the experiment sets of tests are shared:Objective: 10K UserPolicyAttachment MRs
Parallelization: 500 reconcile workers
Poll period: 10min
Node: m5.2xlarge (8vCPU, 32GiB RAM)
Objective: 1K UserPolicyAttachment MRs
Parallelization: 500 reconcile workers
Poll period: 10min
Node: m5.2xlarge (8vCPU, 32GiB RAM)
What's Changed
New Contributors
Full Changelog: crossplane/upjet@v0.10.0...v1.0.0
v0.10.0
Compare Source
The
v0.10.0
release contains some important bug fixes regarding the granular management policies, a fix in the reconciliation logic of the upjet runtime and improvements in the core migration framework. You can bump your provider's upjet dependency by runninggo get github.com/upbound/upjet@v0.10.0
in your provider's root directory.What's Changed
inUse
count to SharedProviderScheduler log statements by @toastwaffle in https://github.com/upbound/upjet/pull/261New Contributors
Full Changelog: crossplane/upjet@v0.9.0...v0.10.0
v0.9.1
Compare Source
This is a patch release that brings backwards-compatibility for upjet-based generated providers so that if they do not explicitly configure an event handler, a default one is configured. Please refer to the discussion in #250 for further details.
What's Changed
Full Changelog: crossplane/upjet@v0.9.0...v0.9.1
v0.9.0
Compare Source
This release adds support for the
spec.initProvider
API and for the granular management policies alpha feature detailed here.The generated example manifests from Terraform registry no longer contain the trailing YAML document separator (
---
).There are numerous improvements and new features introduced to the migration framework to support some new migration cases, such the monolithic official providers to the provider families migration.
The external client for
Terraformed
resources now explicitly requeue, up to 20 retries, a reconciliation request if a shared provider has expired. And only after 20 retries it propagates the error down to the managed reconciler. The ttl-expired error message has also been improved to hint at the--provider-ttl
command-line option.Also status updates and updates to certain annotations (
crossplane.io/external-create-failed
&crossplane.io/external-create-pending
) no longer queue reconciliation requests, which decreases the resource utilization of upjet-based providers. This is especially important when errors happen during the external connecter'sCreate
call, or in general, when an MR is failing to sync successfully.What's Changed
OWNERS.md
andCODEOWNERS
by @turkenf in https://github.com/upbound/upjet/pull/169ControllerConfig
to sizing-guide by @turkenf in https://github.com/upbound/upjet/pull/191New Contributors
Full Changelog: crossplane/upjet@v0.8.0...v0.9.0
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.
This PR has been generated by Renovate Bot.