feat: add possibility to use ACM certificates #7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note
Introduces optional TLS termination via existing ACM certificates and updates generated Helm configs accordingly.
acm_certificate_arninput (with ARN validation); trims/propagates to locals and template rendering inmain.tftemplates/helm-values-bootstrap.tpl.yaml: whenacm_certificate_arnis set, configuresingress-nginxService for NLB with SSL annotations and HTTP backendtemplates/helm-values.tpl.yaml: conditionally removes cert-managerclusterIssuerandtlssections when ACM is used; otherwise preserves Let’s Encrypt defaultsCHANGELOG.md(v0.13.0) and README Inputs table to document the new optionWritten by Cursor Bugbot for commit 2f7f0f2. This will update automatically on new commits. Configure here.