Skip to content
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

Validate - Sub or Ref and TemplateUrl #213

Open
govindrk opened this issue Oct 28, 2021 · 2 comments
Open

Validate - Sub or Ref and TemplateUrl #213

govindrk opened this issue Oct 28, 2021 · 2 comments
Labels

Comments

@govindrk
Copy link

Is your feature request related to a problem? Please describe.

We have lot of nested stacks and reference the same with TemplateURL and parameters - Ref and Sub.

Describe the solution you'd like
When i test the cloud formation for compliance using Guard, the TemplateURL is not validated, both Ref and Sub are also not working.

I am not sure how to get this validate locally and as well in S3. Please provide guidance on how to go about.

regards
govind

@govindrk govindrk added the enhancement New feature or request label Oct 28, 2021
@TheFlexican
Copy link

We also have a use case for cfn-guard be able to validate nested stacks. This would be a huge thumbs up if there was some way of get this to work!

@akshayrane
Copy link
Collaborator

Thanks @govindrk and @TheFlexican for highlighting this issue, noted down that we should be addressing real-life scenarios where CFN template spans across multiple files. We'll research more on how can we achieve that.

Meanwhile, the closest thing that we do support is to use --input-parameters along with --data argument. But even that has a limitation of root keys to be mutually exclusive, as in we don't support taking a union of two files.

Detailed documentation for this feature could be found here under section Dynamic data lookup for inspection via multiple data files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants