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
Is your feature request related to a problem? Please describe.
When using cdk, the template files have the suffix "*.template.json". Looking to run cfn-guard for only the cloudformation templates in the cdk.out directory and not all files within the given directory.
Describe the solution you'd like
Either a cdk specific toggle or a flag to support file regex such as ".template.json" or "projectname.template.json"
Describe alternatives you've considered
Would alternatively need to find the templates and then iteratively invoke cfn-guard
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
I'm using cdk pipelines, that means I also have directories within directories containing json templates. So it would also be a good idea to make the finding of files recursive.
error: Found argument './src/trust.yaml' which wasn't expected, or isn't valid in this context
USAGE:
cfn-guard validate --data <data> <--rules <rules>|--payload>
For more information try --help
Why am I doing this?
I co-locate README.md files that help to describe certain components that are being build by the CloudFormation YAML files.
Is your feature request related to a problem? Please describe.
When using cdk, the template files have the suffix "*.template.json". Looking to run cfn-guard for only the cloudformation templates in the cdk.out directory and not all files within the given directory.
Describe the solution you'd like
Either a cdk specific toggle or a flag to support file regex such as ".template.json" or "projectname.template.json"
Describe alternatives you've considered
Would alternatively need to find the templates and then iteratively invoke cfn-guard
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: