Emre Erkunt
Emre Erkunt
Apparently, Python 3.6 is creating problems. Some of the packages we use does not support Python 3.6 anymore. Please let me know if you will have any issues with deprecating...
## Feature Request **Feature description :** While running against `state` files instead of `plan` files, `terraform-compliance` runs if the state file is created via ; `terraform show -json > state.out.json`...
## Feature Request **Feature description :** #280 **Suggested Solution description ( if you have any ) :** Change the wording where the feature files could not be found there.
### Documentation Request - [ ] Explain what `terraform-compliance` supports, and what does not. - [ ] Explain the interpolation on BDD tests - [ ] Explain how `terraform-compliance` reads...
Store it like ```cucumber Given I have AWS ELB resource defined When it contains internal Then store this resource as aws_public_elb ``` Then retrieve it like ; ```cucumber Given I...
## Question Hello, Gone through the issues but couldn't find one, also spend few hours on the code hacking and mocking some parts to do this, but still couldn't do...
Prevent numeric-looking strings from being coerced into floats by the `jsonify` function to preserve version-like values. ---
Remove resources scheduled for deletion from the parser's state to evaluate the plan's post-apply view. This change ensures that `terraform-compliance` only evaluates resources that will exist after a `terraform apply`....