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.

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

[Enhancement]: aws_amplify_domain_association certificate_settings AMPLIFY_MANAGED should be default #38387

Closed
rsi-mrobinson opened this issue Jul 16, 2024 · 8 comments · Fixed by #40589
Assignees
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/amplify Issues and PRs that pertain to the amplify service.
Milestone

Comments

@rsi-mrobinson
Copy link

Description

the newly added (>=5.57.0) certificate_settings attribute should default to AMPLIFY_MANAGED rather than null. Existing resources appear to result in plans where the certificate settings are being removed, despite amplify managed domains being the default up to this point. The new certificate setting block should respect this an only be required to override the default settings.

Affected Resource(s) and/or Data Source(s)

aws_amplify_domain_association

Potential Terraform Configuration

No response

References

No response

Would you like to implement a fix?

None

@rsi-mrobinson rsi-mrobinson added the enhancement Requests to existing resources that expand the functionality or scope. label Jul 16, 2024
Copy link

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@terraform-aws-provider terraform-aws-provider bot added the needs-triage Waiting for first response or review from a maintainer. label Jul 16, 2024
@justinretzolk justinretzolk added service/amplify Issues and PRs that pertain to the amplify service. and removed needs-triage Waiting for first response or review from a maintainer. labels Jul 17, 2024
@justinretzolk
Copy link
Member

Hey @rsi-mrobinson 👋 Thank you for taking the time to raise this! To make sure I understand -- you're saying that if you update the version and make no other configuration changes, resources are being replaced on the next apply?

@rsi-mrobinson
Copy link
Author

That's correct, if you upgrade to 5.57 or above without making changes to this resource, the plan shows a change to remove the default amplify managed dns

@aayushsss1
Copy link

Hey @justinretzolk @rsi-mrobinson I can take this issue up, just to be clear the only change would be to add
Default : "AMPLIFY_MANAGED" here right?

},
names.AttrType: {
Type: schema.TypeString,
Required: true,
ValidateDiagFunc: enum.Validate[types.CertificateType](),
},
"custom_certificate_arn": {

@rsi-mrobinson
Copy link
Author

That's what I'm thinking

Copy link

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

@github-actions github-actions bot added this to the v5.82.0 milestone Dec 17, 2024
@github-actions github-actions bot removed the prioritized Part of the maintainer teams immediate focus. To be addressed within the current quarter. label Dec 19, 2024
Copy link

This functionality has been released in v5.82.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 19, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.