Andrew Best

Same problems here. Seeing the same errors. Turns out that an underlying OS update had re-enabled `systemd-resolve`. A quick ```shell systemctl disable systemd-resolved.service systemctl stop systemd-resolved ``` and were back...

I just hit this with a customer environment. In our case, while building out the Terraform code I had initially configured the TFE Provider using a simple ```hcl provider "tfe"...

Workaround: ```terraform provider "tfe" { token = data.vault_generic_secret.tfc.data["token"] } locals { vault_tfc_token = { dev = { backend = "acl_cpt/tfc_dev" role = "tfc-orgname-dev-org-token" } prod = { backend = "acl_cpt/tfc_prod"...

A little late but, Happy Birthday to this issue. 🎂 To the maintainers, can we get a statement about why support for other VCS providers is blocked? IS it a...

Probably also worth mentioning that the `r/tfe_notification_configuration` resource will also need to add support for the new triggers available under Notifications now: ...

Can I second what @scarolan has stated above? I have supplied my own public key via the `import_key` var and the public key is not being inserted into the `~ubuntu/.ssh/authorized_keys`...

Ive tracked down the root cause of this behaviour. See https://github.com/terraform-providers/terraform-provider-azurerm/issues/4983 I will leave this issue open for the next poor sap that gets bitten by it.

Hey @ryancbutler, suggest you use the template available [here](https://github.com/terraform-providers/terraform-provider-azurerm/issues) to better flesh out the explanation in this fault.

Hey @erindatkinson, I got all excited about using the postgresql provider to do the DB seeding but then I ran into https://github.com/terraform-providers/terraform-provider-postgresql/issues/2 at a screaming pace. Le sigh.

A wild blocker appeared. https://github.com/terraform-providers/terraform-provider-postgresql/issues/107