Sander Blue

If we haven't done so already, we should also add a snippet in the documentation warning users that sensitive data _could_ be within logs when using TRACE level logging, such...

For anyone still experiencing this issue, do you still see the issue if you run the `terraform` command using the `-parallelism` option set to a lower number than the default...

After further investigation, it looks like the problem has to do with how the HCL is being constructed in the reported scenarios. @trustthewhiterabbit's HCL is actually looping over the same...

Note this can also be accomplished using `count` as well. e.g. ```hcl locals { apps = [ "Example App Name 1", "Example App Name 2", ] custom_tags = { "tag-key-1"...

Hi @jaecktec, the `newrelic_synthetics_alert_condition` resource is a legacy resource and will likely not be receiving any updates. It calls an old legacy API which has been deprecated. Our [documentation](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/synthetics_alert_condition) recommends...

Hi @rrbadam, this GitHub Action should work just fine with `workflow_dispatch` (just confirmed it works). Assuming you have your GitHub secrets set up properly, I'm not sure why it would...

Hi @juupas, thanks for reporting. So far I haven't been able to reproduce the issue. That error message typically means credentials are missing. Can you double check your API key...

Agreed we should have better error messaging :)

Agreed, this should be updated. Thanks for reaching out 🙂

Sure thing. Will take a look.