Certificates are now based on AWS by default
Closed this issue · 4 comments
Since commit 7fd722a#diff-fd3213de7fa589296976a86d65cc2496 it seems that using AWS is the only way to get the certificates in place. Unless it is possible to put the certificates somewhere, before calling Curator?
What is the way to go here, since we are not using AWS for our local development machine setup?
Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, Certificate ARN can only be of types: ( arn:aws:acm | arn:aws:iam | s3: ) (file: /vagrant/aempuppet/modules/aem_curator/manifests/reconfig_pre_aem.pp, line: 236, column: 9) (file: /vagrant/aempuppet/modules/aem_curator/manifests/config_author_primary.pp, line: 119) on node author.localhost.com
The error message should be updated from "Certificate ARN can only be of types: ( arn:aws:acm | arn:aws:iam | s3: )" to "Certificate ARN can only be of types: ( arn:aws:acm | arn:aws:iam | s3: | http: | https: | file: )"
@henrykuijpers I belive @Carnifrex is right, this more of an issue around the error message. While it actually supports http and file as well.
@henrykuijpers & @Carnifrex Changes are included in release 3.11.0. Therefor I'll close this ticket. please re-open it if anything is still unclear.