You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 16, 2022. It is now read-only.
Description: TEST
Parameters:
ACMCertificateARN:
Description: ARN for certificate to be used by CloudFront
Type: String
Resources:
DistributionConfig:
Type: AWS::CloudFront::Distribution
Properties:
DistributionConfig:
Enabled: true
ViewerCertificate:
AcmCertificateArn: !Ref ACMCertificateARN
And, replacing the Ref function that references a template parameter (AcmCertificateArn: !Ref ACMCertificateARN) by a string works.
At this stage, I'm unsure of the cause of this validation failure. I suspect that the validator.isArn function is expecting a string starting with arn:aws as per
Thanks! You should be able to define a simple ARN on the CLI with --parameters ACMCertificateARN="arn:aws:something:something:something".
As cfn-lint attempts to find all errors, if a parameter isn't given, the system will guess. In the case of empty parameters, it will be type_input_ParameterName as you have seen.
If a parameter default is given, cfn-lint will use this value by default.
I ran into this too. Please consider changing the error message so that it's more clear what the appropriate response is (either use --params or --no-guess-params)
I tried some variations, but I wasn't able to apply the workaround with the API (where's the --no-gess-params option in ValidationOptions?) Reverted to pre-guessing version :(
First of all, thanks for this tool 👍
The following template:
fails to validate:
And, replacing the Ref function that references a template parameter (
AcmCertificateArn: !Ref ACMCertificateARN
) by a string works.At this stage, I'm unsure of the cause of this validation failure. I suspect that the
validator.isArn
function is expecting a string starting witharn:aws
as percfn-lint/src/validator.ts
Line 1436 in 2e2a767
The text was updated successfully, but these errors were encountered: