feat(acm): add support for ACM exportable public certificates

[frankhefeng]

Issue # (if applicable)

Closes #35078.

Reason for this change

We want to use ACM exportable public certificates to replace all those certificates purchased from another vendor

Description of changes

Add certificateExportEnabled in acm.Certificate Construct

Describe any new or updated permissions being added

N/A

Description of how you validated changes

Unit updated to cover new certificateExportEnabled property

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[aws-cdk-automation]

(This review is outdated)

[aws-cdk-automation]

(This review is outdated)

Dismissing outdated PRLinter review.

[frankhefeng]

version of package aws-cdk/aws-service-spec updated to get new L1 Construct with the new CertificateExport property of AWS::CertificateManager::Certificate

[frankhefeng]

Exemption Request

This MR does not implement integration testing for the following reason:

To request an ACM exportable public certificate, a domain and a Route53 hosted zone are required. This is difficult in CI.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #35079 has been dequeued. The pull request could not be merged. This could be related to an activated branch protection or ruleset rule that prevents us from merging. (details: 1 review requesting changes and 1 approving review by reviewers with write access.).

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

Pull request has been modified.

Pull request has been modified.

[frankhefeng]

hey @vishaalmehrishi , may I have some instruction what should I do for next step? Thanks

[vishaalmehrishi]

hey @vishaalmehrishi , may I have some instruction what should I do for next step? Thanks

Hi @frankhefeng , yes, please take a look at this comment: #35079 (comment)

[frankhefeng]

hey @vishaalmehrishi , may I have some instruction what should I do for next step? Thanks

Hi @frankhefeng , yes, please take a look at this comment: #35079 (comment)

Updated

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #35079 has been dequeued. The pull request could not be merged. This could be related to an activated branch protection or ruleset rule that prevents us from merging. (details: 1 review requesting changes and 1 approving review by reviewers with write access.).

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[vishaalmehrishi]

@Mergifyio requeue

[mergify]

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.