-
Notifications
You must be signed in to change notification settings - Fork 594
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
Throw the E3510 when the policy is not created because of the condition #3456
Comments
Using the latest version of cfn-lint and this condition I cannot replicate this error. "IngestionCommonResourcesCreateApplicationLoadBalancerauthEnableConditionF2B09238": {
"Fn::Not": [
{
"Fn::Equals": [
{"Ref": "AuthenticationSecretArn"},
""
]
}
]
} |
I wrote a cloudformation example template as below:
execute: cfn-lint -e -t ./E3510-test.yaml got below error: E3510 {'Ref': 'secretArn'} does not match '(^arn:(aws|aws-cn|aws-us-gov):[^:]+:[^:](:(?:\d{12}|\|aws)?:.+|)|\*)$' when 'Ref' is resolved |
This is similar to #3378. The error is coming from the fact that I can leave The way we typically see this solved is something like: or |
Is this feature request related to a new rule or cfn-lint capabilities?
No response
Describe the feature you'd like to request
Hello,
We have below use case.
We have a cloudformation template to create Policy as below:
And AuthenticationSecretArn is input parameter as below:
Now the cfn-lint throw the below error:
E3510 {'Ref': 'AuthenticationSecretArn'} does not match '(^arn:(aws|aws-cn|aws-us-gov):[^:]+:[^:](:(?:\d{12}|\|aws)?:.+|)|\*)$' when 'Ref' is resolved
Our use case is the Policy is controlled by a condition
IngestionCommonResourcesCreateApplicationLoadBalancerauthEnableConditionF2B09238
If the AuthenticationSecretArn is '', condition will be false and policy will not be created.
Could you think about this use case and do some change to support this case?
Thanks,
Mingtong
Describe the solution you'd like
If the AuthenticationSecretArn is '', condition will be false and policy will not be created.
Could you think about this use case and do some change to support this case?
Additional context
No response
Is this something that you'd be interested in working on?
Would this feature include a breaking change?
The text was updated successfully, but these errors were encountered: