-
Notifications
You must be signed in to change notification settings - Fork 304
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
inconsistent behaviour for resources that can have repeated blocks defined with HCL2 #1006
Comments
@crivetechie We don't lock dependencies, but we typically only bump them if there is a reported issue. Can you confirm if updating this dependency solves your problem? |
@jalseth updating the dependency solves the problem, however it introducing a list of changes that will break existing policies. I've opened a PR in my fork to demonstrate the impact of upgrading to latest version: https://github.com/crivetechie/conftest/pull/1/files |
I think we should bump if the new version is more accurate according to the Terraform JSON syntax specification [1]. I haven't had time to review the spec in detail, but if you can confirm that the new output is aligned with the spec, feel free to open a PR to bump the dep. [1] https://developer.hashicorp.com/terraform/language/syntax/json |
Hello, we are having some issues writing policies for resource that may contain repeated blocks.
It looks like the behaviour of conftest is to produce an object when there's a single block and an array if the block is repeated.
See the example below definining two kubernetes_deployment resources, the first using a single container block and the second using 2 containers blocks
the above is parsed as
as you can see
spec.template.spec.container
inexample-multiple-blocks
is an array, it is an object inexample-single-block
Accoriding to #266 I was expecting this to be resolved but it isn't, looks like conftest is using version 0.3.1 of hcl2json lib which doesn't include the fix.
I am wondering if there was a decision to lock to [email protected] to avoid introducing breaking changes and if there's any plan for upgrading to latest version. Thank you!
The text was updated successfully, but these errors were encountered: