Skip to content

Update module github.com/cert-manager/cert-manager to v1.20.1#445

Merged
cert-manager-prow[bot] merged 1 commit intocert-manager:mainfrom
erikgb:upgrade-cm-1-20
Mar 29, 2026
Merged

Update module github.com/cert-manager/cert-manager to v1.20.1#445
cert-manager-prow[bot] merged 1 commit intocert-manager:mainfrom
erikgb:upgrade-cm-1-20

Conversation

@erikgb
Copy link
Copy Markdown
Member

@erikgb erikgb commented Mar 27, 2026

This PR extends #434 by adding the new Azure DNS zoneType field to older API versions. This appears to be the correct/simplest thing to do, but please let me know if another solution is preferred.

Closes #434

@cert-manager-prow cert-manager-prow Bot added dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Mar 27, 2026
@erikgb erikgb requested a review from Copilot March 27, 2026 12:02
@erikgb
Copy link
Copy Markdown
Member Author

erikgb commented Mar 27, 2026

/cc @hjoshi123 @inteon

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates cmctl’s cert-manager dependency to v1.20.0 and extends the internal ACME API/conversion layer so the new Azure DNS zoneType field round-trips through older ACME API versions.

Changes:

  • Bump github.com/cert-manager/cert-manager to v1.20.0 (and associated indirect deps).
  • Add zoneType to ACME Issuer AzureDNS structs in v1alpha2, v1alpha3, and v1beta1 internal APIs.
  • Update generated ACME conversion functions to copy zoneType between versioned types and the internal hub type.

Reviewed changes

Copilot reviewed 9 out of 10 changed files in this pull request and generated 4 comments.

Show a summary per file
File Description
pkg/convert/internal/apis/acme/v1beta1/zz_generated.conversion.go Copy ZoneType during v1beta1 ↔ internal ACME conversions.
pkg/convert/internal/apis/acme/v1beta1/types_issuer.go Add AzureZoneType and ZoneType field to v1beta1 AzureDNS provider type.
pkg/convert/internal/apis/acme/v1alpha3/zz_generated.conversion.go Copy ZoneType during v1alpha3 ↔ internal ACME conversions.
pkg/convert/internal/apis/acme/v1alpha3/types_issuer.go Add AzureZoneType and ZoneType field to v1alpha3 AzureDNS provider type.
pkg/convert/internal/apis/acme/v1alpha2/zz_generated.conversion.go Copy ZoneType during v1alpha2 ↔ internal ACME conversions.
pkg/convert/internal/apis/acme/v1alpha2/types_issuer.go Add AzureZoneType and ZoneType field to v1alpha2 AzureDNS provider type.
pkg/convert/internal/apis/acme/v1/zz_generated.conversion.go Copy ZoneType during cert-manager v1 ↔ internal ACME conversions.
pkg/convert/internal/apis/acme/types_issuer.go Add AzureZoneType and ZoneType to the internal ACME hub type.
go.mod Bump cert-manager to v1.20.0 and refresh some indirect requirements.
go.sum Update module checksums consistent with the dependency bump.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread pkg/convert/internal/apis/acme/v1alpha3/types_issuer.go
Comment thread pkg/convert/internal/apis/acme/v1beta1/types_issuer.go
Comment thread pkg/convert/internal/apis/acme/types_issuer.go
Comment thread pkg/convert/internal/apis/acme/v1alpha2/types_issuer.go
@hjoshi123
Copy link
Copy Markdown

Mostly LGTM but had a minor comment
@erikgb do you think its worth it add some tests in https://github.com/cert-manager/cmctl/blob/main/test/integration/ctl_convert_test.go here since we changed the old api versions with some new fields?

Comment thread pkg/convert/internal/apis/acme/types_issuer.go Outdated
@erikgb
Copy link
Copy Markdown
Member Author

erikgb commented Mar 28, 2026

do you think its worth it add some tests in https://github.com/cert-manager/cmctl/blob/main/test/integration/ctl_convert_test.go here since we changed the old api versions with some new fields?

No, I don't think it's required to add more testing. The fuzz-tests really cover a lot. 😅

Signed-off-by: Erik Godding Boye <egboye@gmail.com>
@erikgb erikgb changed the title Update module github.com/cert-manager/cert-manager to v1.20.0 Update module github.com/cert-manager/cert-manager to v1.20.1 Mar 28, 2026
@erikgb erikgb requested a review from inteon March 28, 2026 14:13
@hjoshi123
Copy link
Copy Markdown

LGTM but probably Tim should approve it too since he requested changes
/lgtm

@cert-manager-prow cert-manager-prow Bot added the lgtm Indicates that a PR is ready to be merged. label Mar 29, 2026
@erikgb
Copy link
Copy Markdown
Member Author

erikgb commented Mar 29, 2026

Thanks @hjoshi123! I have fixed the (valid) remark from @inteon now, and if you agree to the simple approach taken here, we should be good to merge. We need to upgrade the cert-manager dependency and should probably cut a new release soonish. 🤠

/approve

@cert-manager-prow
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: erikgb

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@cert-manager-prow cert-manager-prow Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 29, 2026
@cert-manager-prow cert-manager-prow Bot merged commit 70f0307 into cert-manager:main Mar 29, 2026
5 checks passed
@hjoshi123
Copy link
Copy Markdown

Yes, given the change requested was simple enough, I feel approval is valid :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants