Skip to content

Conversation

@akash1810
Copy link
Member

What does this change?

Typically, the DeletionPolicy is set to support CloudFormation imports. The AWS::CertificateManager::Certificate resource does not yet support CFN imports1, so stop setting DeletionPolicy and UpdateReplacePolicy.

How to test

See CI and updated snapshots.

Checklist

  • I have listed any breaking changes, along with a migration path 2
  • I have updated the documentation as required for the described changes 3

Footnotes

  1. See also https://github.com/guardian/cdk/pull/390#discussion_r608459080.

  2. Consider whether this is something that will mean changes to projects that have already been migrated, or to the CDK CLI tool. If changes are required, consider adding a checklist here and/or linking to related PRs.

  3. If you are adding a new construct or pattern, has new documentation been added? If you are amending defaults or changing behaviour, are the existing docs still valid?

@changeset-bot
Copy link

changeset-bot bot commented Jan 23, 2026

🦋 Changeset detected

Latest commit: 640ce2d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@guardian/cdk Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@akash1810 akash1810 added the feature Departmental tracking: work on a new feature label Jan 23, 2026
Typically, the `DeletionPolicy` is set to support CloudFormation imports.
The `AWS::CertificateManager::Certificate` resource does not yet support CFN imports.

See https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/resource-import-supported-resources.html.
@akash1810 akash1810 force-pushed the aa/acm-certificate-policy branch from fd83c60 to 640ce2d Compare January 23, 2026 12:10
@akash1810 akash1810 marked this pull request as ready for review January 23, 2026 12:13
@jacobwinch
Copy link
Contributor

Although these properties don't really seem to be necessary, does removing them provide any particular benefit for users?

If not, I'd be tempted to leave it as is to avoid adding friction for pattern users who are relying on automated library upgrades.

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

Labels

feature Departmental tracking: work on a new feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants