grahamhar

@barryib any chance you can open a PR for this, I really need support for this too :)

We wrap the setup apply and destroy in a fixture: ```python @pytest.fixture(scope='module') def output(scenarios_dir, tf_vars, scenario): print(f'Setup starting for {scenario}') tf = tftest.TerraformTest(scenario, scenarios_dir) tf.setup() try: tf.apply(tf_vars=tf_vars) print(f'setup complete for...

@ludoo Sorry I probably should have provided more explanation, let me provide a few examples of how I think the approach I suggested helps. 1. Issue with Terraform code under...

Yes you get a test pass which in our use case is what we want. If that is not what you want add a pytest.fail to the except block

I've just taken a look at trying to add a diff suppress function for this, but I've been hit by a [bug in the terraform plugin sdk](https://github.com/hashicorp/terraform-plugin-sdk/issues/477). As these only...

I've just hit this issue also, I added some debug and the values for the timeout report to be correct. Could the issue be that the main home bridge code...

I am looking at using commitizen in a monorepo too and I hit issues when trying to do this by using different `tag_format` to allow different tags to work. I...

> That'd be really nice, I'd like to see an example with what we currently have @woile so this isn't strictly with what we have now it would need the...

Our CI validates that the commits only have files for the component in the scope, build fails so that doesn't get to trunk and won't be released. We are also...

I'm using 5.0.7 and saw the reported issue when updating to to 5.0.8