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-azure to v1 - autoclosed #91

Closed
wants to merge 1 commit into from
Closed

chore(deps): update dependency upbound/provider-azure to v1 - autoclosed #91

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 4, 2024 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Update Change
upbound/provider-azure major v0.42.1 -> v1.4.0

Release Notes

upbound/provider-azure (upbound/provider-azure)

v1.4.0

Compare Source

The v1.4.0 release introduces a new resource BastionHost.network.azure.upbound.io/v1beta1, bug fixes, and dependency updates.

What's Changed

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

v1.3.0

Compare Source

The v1.3.0 release introduces new resources, bug fixes, enhancements, and dependency updates.

Support for New Resources
  • PimActiveRoleAssignment.authorization.azure.upbound.io/v1beta1
  • PimEligibleRoleAssignment.authorization.azure.upbound.io/v1beta1
Bug Fixes and Enhancements

What's Changed

New Contributors

Full Changelog: crossplane-contrib/provider-upjet-azure@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, adding a new resource VirtualMachineRunCommand.compute, 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 RedisCache.cache.azure.upbound.io/v1beta2 resource's spec.forProvider, with this release we can see the spec.forProvider.redisConfiguration field as an object:
 spec:
   forProvider:
     capacity: 1
     enableNonSslPort: false
     family: P
     location: West Europe
     minimumTlsVersion: "1.2"
     publicNetworkAccessEnabled: true
     redisConfiguration:
       maxmemoryDelta: 2
       maxmemoryPolicy: allkeys-lru
       maxmemoryReserved: 2
     redisVersion: "6"
     resourceGroupName: example-redis-ftest
     skuName: Premium
  • If we look at the v1beta1 YAML output of the resource, we see the field as a list:
spec:
  forProvider:
    capacity: 1
    enableNonSslPort: false
    family: P
    location: West Europe
    minimumTlsVersion: "1.2"
    publicNetworkAccessEnabled: true
    redisConfiguration:
    - maxmemoryDelta: 2
      maxmemoryPolicy: allkeys-lru
      maxmemoryReserved: 2
    redisVersion: "6"
    resourceGroupName: example-redis-ftest
    skuName: Premium

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

New Contributors

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

v1.1.0

Compare Source

The v1.1.0 release introduces MR metrics, a new resource, 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 a New Resource
  • Deployment.cognitiveservices.azure.upbound.io/v1beta1
Bug Fixes and Enhancements

What's Changed

New Contributors

Full Changelog: crossplane-contrib/provider-upjet-azure@v1.0.1...v1.1.0

v1.0.1

Compare Source

The release v1.0.1 introduces:

  • Sets the Azure partner tracking GUID to a9cee75d-8f11-42e4-bc19-953757f4ea3c in the requests that are made by the provider.
  • Adds these two words to the UserAgent header.
    • The provider name/version such as crossplane-provider-upjet-azure/v1.0.1
    • The CPU architecture & operating system name the provider is running on, such as (arm64-darwin)

The resulting User-Agent header value looks like the following:

HashiCorp/go-azure-sdk (Go-http-Client/1.1 capabilities/2023-11-01) HashiCorp Terraform/ (+https://www.terraform.io) Terraform Plugin SDK/2.10.1 terraform-provider-azurerm/dev crossplane-provider-upjet-azure/v1.0.1 (arm64-darwin) pid-a9cee75d-8f11-42e4-bc19-953757f4ea3c

What's Changed

Full Changelog: crossplane-contrib/provider-upjet-azure@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 3.57.0 to 3.95.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.

Support for a New Resource
  • WorkspaceRootDbfsCustomerManagedKey.databricks.azure.upbound.io/v1beta1
Bug Fixes and Enhancements
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
linuxwebapp.web.azure.upbound.io/linuxappexample   True     True    linuxappexample   5m46s

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.

API Changes
  • Changed external name configuration of the following resources:
    • APIOperationPolicy.apimanagement.azure.upbound.io/v1beta1
    • APIPolicy.apimanagement.azure.upbound.io/v1beta1
    • Policy.apimanagement.azure.upbound.io/v1beta1
    • ProductPolicy.apimanagement.azure.upbound.io/v1beta1
  • API.apimanagement.azure.upbound.io/v1beta1 => spec.forProvider.revision is now required parameter.
  • Logger.apimanagement.azure.upbound.io/v1beta1 => spec.forProvider.eventhub.connectionString is now optional parameter.
  • HybridRunBookWorkerGroup.automation.azure.upbound.io/v1beta1 => added reference and selector for spec.forProvider.automationAccountName field.
  • BotChannelWebChat.botservice.azure.upbound.io/v1beta1 => spec.forProvider.siteNames has been replaced with spec.forProvider.site code block.
  • WorkspaceCustomerManagedKey.databricks.azure.upbound.io/v1beta1 => This resource has been deprecated and will be removed in future versions of provider. Please use the WorkspaceRootDbfsCustomerManagedKey resource instead.
  • FlexibleServer.dbforpostgresql.azure.upbound.io/v1beta1 => status.atProvider.identity.{principalId,tenantId} have been removed.
  • LabServiceLab.labservices.azure.upbound.io/v1beta1 => spec.forProvider.connectionSetting is now required parameter.
  • LinuxWebApp.web.azure.upbound.io/v1beta1 => spec.forProvider.siteConfig.autoHealSetting.trigger.statusCode.win32Status has been replaced with spec.forProvider.siteConfig.autoHealSetting.trigger.statusCode.win32StatusCode.
  • LinuxWebAppSlot.web.azure.upbound.io/v1beta1 => spec.forProvider.siteConfig.autoHealSetting.trigger.statusCode.win32Status has been replaced with spec.forProvider.siteConfig.autoHealSetting.trigger.statusCode.win32StatusCode.
  • WindowsWebApp.web.azure.upbound.io/v1beta1 => spec.forProvider.siteConfig.autoHealSetting.trigger.statusCode.win32Status has been replaced with spec.forProvider.siteConfig.autoHealSetting.trigger.statusCode.win32StatusCode.
  • WindowsWebAppSlot.web.azure.upbound.io/v1beta1 => spec.forProvider.siteConfig.autoHealSetting.trigger.statusCode.win32Status has been replaced with spec.forProvider.siteConfig.autoHealSetting.trigger.statusCode.win32StatusCode.

What's Changed

New Contributors

Full Changelog: crossplane-contrib/provider-upjet-azure@v0.42.2...v1.0.0

v0.42.2

Compare Source

The release v0.42.2 introduces:

What's Changed

Full Changelog: crossplane-contrib/provider-upjet-azure@v0.42.1...v0.42.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 Apr 4, 2024
@renovate renovate bot force-pushed the renovate/upbound-provider-azure-1.x branch from 21c0d60 to 672a477 Compare April 4, 2024 20:26
@renovate renovate bot force-pushed the renovate/upbound-provider-azure-1.x branch from 672a477 to 54da0eb Compare April 25, 2024 23:05
@renovate renovate bot force-pushed the renovate/upbound-provider-azure-1.x branch from 54da0eb to 30882b2 Compare May 22, 2024 16:31
@renovate renovate bot force-pushed the renovate/upbound-provider-azure-1.x branch from 30882b2 to 346b766 Compare June 13, 2024 16:31
@renovate renovate bot force-pushed the renovate/upbound-provider-azure-1.x branch from 346b766 to 07d0b3b Compare July 4, 2024 13:10
@renovate renovate bot changed the title chore(deps): update dependency upbound/provider-azure to v1 chore(deps): update dependency upbound/provider-azure to v1 - autoclosed Jul 11, 2024
@renovate renovate bot closed this Jul 11, 2024
@renovate renovate bot deleted the renovate/upbound-provider-azure-1.x branch July 11, 2024 10:18
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.
0 participants