Richard Vaughn

> @jcogilvie if you are using a GitHub App to auth in your Terraform provider - then the app you are referencing in your resource will need to be public...

I did accomplish the same effect by using setsubtract(), but it would be much cleaner if the data lookup supported the idea of excluding specific tags from the results. `setsubtract(values(data.tfe_workspace_ids.aws.ids),...

The odd-related flip side of this is there is no data source to look up all the teams that currently have access to a workspace. You have to already know...

This issue is definitely still a bug. The provider should at least handle the error that it cannot be removed and move on gracefully.

Since it has been deemed that volume_tags is incompatible with root_block_device and ebs_block_device tag usage, perhaps it would be better to revisit default_tags interacting with those two? volume_tags are much...

Any plans to implement default_tags for ebs/root block devices? This is making tagging enforcement quite complicated and slowing our adoption of default_tags.

Is this being included in the 5.0.0 roadmap? This feature is really important for cost tracking.

Has this gotten any attention? This is basically preventing PR requirements from being enabled via the terraform provider. We have new repositories going out that no longer have correct branch...

This seems to have been resolved in the latest versions of the provider and terraform enterprise.