v1.6.1

This release includes updates to the go.mod file to address security vulnerabilities.

What's Changed

• Update go.mod dependencies release-1.6 [SECURITY] by @turkenf in #178

Full Changelog: v1.6.0...v1.6.1

v1.6.0

The v1.6.0 release introduces the Terraform provider upgrade from 2.47.0 to 2.53.1, support for Upbound authentication, bug fixes, enhancements, and dependency updates.

What's Changed

• Update alpine Docker tag to v3.20.3 by @renovate in #151
• Update dependency ubuntu to v24 by @renovate in #157
• Update build submodule and set XPKG_CLEANUP_EXAMPLES_ENABLED = true by @turkenf in #160
• Remove workflows no longer needed. by @jeanduplessis in #163
• consume golangci-lint 1.61.0 by @erhancagirici in #164
• Use standalone crddiff tool by @turkenf in #165
• add support for Upbound auth by @erhancagirici in #166
• Update Terraform provider version to 2.53.1 by @erhancagirici in #167
• Stop using deprecated upbound/official-provider-ci workflows by @jeanduplessis in #168
• Ignore lateinitialize for owner field in group resource by @turkenf in #171

New Contributors

• @erhancagirici made their first contribution in #164

Full Changelog: v1.5.0...v1.6.0

v1.5.0

The v1.5.0 release introduces support for ManagedIdentity and OIDC authentication methods, and dependency updates. With this release we cleaned uptest specific codes/placeholders from the examples in the marketplace.

What's Changed

• Add support for ManagedIdentity and OIDC authentication methods by @gravufo in #139
• Bump upjet to the commit 3afbb77 by @turkenf in #152
• Update build submodule by @turkenf in #156

New Contributors

• @gravufo made their first contribution in #139

Full Changelog: v1.4.1...v1.5.0

v1.4.1

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

What's Changed

• [Backport release-1.4] Bump upjet to the commit 3afbb77 by @github-actions in #154

Full Changelog: v1.4.0...v1.4.1

v1.4.0

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

What's Changed

• Update alpine Docker tag to v3.20.1 by @renovate in #137
• Update dependency go to v1.22.4 by @renovate in #116
• Use crossplane/build submodule by @turkenf in #135
• Update module github.com/hashicorp/go-retryablehttp to v0.7.7 [SECURITY] by @renovate in #138
• Update alpine Docker tag to v3.20.2 by @renovate in #142
• Bump uptest version to v0.13.0 by @turkenf in #144
• Only apply CRD API conversions for converting between singleton list and embedded objects APIs by @turkenf in #143
• Fix Example in Permissiongrant Managed Resource by @jgmartinez in #146
• Update README and GitHub templates by @jeanduplessis in #149
• Bump Upjet to commit 2e361ad3b6e6 by @mergenci in #150

New Contributors

• @jgmartinez made their first contribution in #146

Full Changelog: v1.3.0...v1.4.0

v1.3.0

The release v1.3.0 generates the secret references under spec.initProvider API trees and updates dependencies.

What's Changed

• Update alpine Docker tag to v3.20.0 by @renovate in #134
• Generate secret references for the sensitive fields under the spec.initProvider API tree by @ulucinar in #136

Full Changelog: v1.2.0...v1.3.0

v1.2.0

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 Location.conditionalaccess.azuread.upbound.io/v1beta2 resource's spec.forProvider, with this release we can see the spec.forProvider.ip field as an object:

spec:
  forProvider:
    displayName: IP Named Location
    ip:
      ipRanges:
      - 1.1.1.1/32
      - 2.2.2.2/32
      trusted: true

• If we look at the v1beta1 YAML output of the resource, we see the field as a list:

spec:
  forProvider:
    displayName: IP Named Location
    ip:
    - ipRanges:
      - 1.1.1.1/32
      - 2.2.2.2/32
      trusted: true

For a detailed overview of the implementation, please see crossplane/upjet#387 and crossplane/upjet#400

What's Changed

• Add needs:triage label to issue template by @turkenf in #131
• Convert all singleton lists in the MR APIs to embedded objects by @ulucinar in #123
• Bump crossplane-runtime version to consume the fix of MR metrics by @sergenyalcin in #132
• Bump upjet to the latest commit by @sergenyalcin in #133

Full Changelog: v1.1.0...v1.2.0

v1.1.0

The v1.1.0 release introduces MR metrics, bug fixes, 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 crossplane/crossplane-runtime#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 crossplane/crossplane-runtime#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"}.

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 crossplane/upjet#391 (comment).

What's Changed

• Remove GitHub issue triage workflow by @turkenf in #121
• Update module sigs.k8s.io/controller-runtime to v0.17.3 by @renovate in #120
• Update kubernetes patches to v0.29.4 by @renovate in #122
• Rename the repo name for reusable workflows used by @turkenf in #129
• Introduce MR metrics by @mergenci in #127

New Contributors

• @mergenci made their first contribution in #127

Full Changelog: v1.0.0...v1.1.0

v1.0.0

In the v1.0.0 release, we've upgraded the underlying Terraform provider version from 2.41.0 to 2.47.0.

This release includes bug fixes, and updating dependencies, with the most significant ones detailed below.

• 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.
• Bump crossplane/upjet to the commit 50919febc5ab

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
application.applications.azuread.upbound.io/example   True     True    /applications/de08fd76-7ddc-4cb0-a3ac-03907da70847   2m29s

This used to be first the READY column and then the SYNCED column previously. Please see crossplane/upjet#360 for further details.

What's Changed

• Comprehensive Issue Template Update: Assisting Users in Better Issue Definition by @turkenf in #98
• Update alpine Docker tag to v3.19.1 by @renovate in #92
• Update kubernetes packages to v0.29.1 by @renovate in #93
• Update module golang.org/x/crypto to v0.17.0 [SECURITY] by @renovate in #95
• Update kubernetes patches to v0.29.2 by @renovate in #99
• Switch from the NoFork terminology to the TerraformPluginSDK terminology and bump dependencies by @turkenf in #100
• Update module sigs.k8s.io/controller-runtime to v0.17.2 by @renovate in #104
• Update module github.com/cloudflare/circl to v1.3.7 [SECURITY] by @renovate in #103
• Consume the reusable workflows from upbound/uptest@standard-runners by @ulucinar in #106
• Applying license changes by @sergenyalcin in #111
• Bump Terraform provider version to v2.47.0 by @turkenf in #110
• Update module google.golang.org/protobuf to v1.33.0 [SECURITY] by @renovate in #112
• Update kubernetes patches to v0.29.3 by @renovate in #114
• Set log.Default's output to io.Discard by @ulucinar in #115
• Change the value of meta.crossplane.io/source by @sergenyalcin in #117

New Contributors

• @sergenyalcin made their first contribution in #111

Full Changelog: v0.15.3...v1.0.0

v0.15.3

The release v0.15.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

• [Backport release-0.15] Set log.Default's output to io.Discard by @github-actions in #118
• [Backport release-0.15] Change the value of meta.crossplane.io/source by @github-actions in #119

Full Changelog: v0.15.2...v0.15.3