Brian Flad

Thanks for raising this, @Noel-Jones 👍 Over in the [`tls_locally_signed_cert` resource](https://registry.terraform.io/providers/hashicorp/tls/latest/docs/resources/locally_signed_cert#early_renewal_hours) and [`tls_self_signed_cert` resource](https://registry.terraform.io/providers/hashicorp/tls/latest/docs/resources/self_signed_cert#early_renewal_hours), they include an optional `early_renewal_hours` attribute. This seems like a reasonable precedent for this type of...

It sounds like there is some potential conflation of concerns because any particular schema definition recommendations will cause provider developers to try to choose an appropriate practitioner experience for them....

Related feature request issue: https://github.com/hashicorp/terraform-plugin-framework/issues/597 For any reviewers, please note that the current `attr.Value` interface change is a breaking change since it would force all existing custom type implementations to...

Hi @alexhung 👋 Thank you for raising this. Setting an attribute `Sensitive` flag should signal to Terraform across the plugin protocol that it should treat any values of that attribute...

@bendbennett / @jar-b anything else need to happen here? Implementation change looks good to me 😄

I have also been receiving the "GitHub request timed out" pop-ups the last 2 weeks or so, constantly, in both personal GitHub repository and my work GitHub repository workspaces. Never...

Hi @tylerFowler 👋 Thank you for raising this! The design scope of this tool was _intended_ to be for provider documentation only. That being said, I have added this to...

Hi @tylerFowler 👋 As alluded to above, timeouts configuration will display in the default tfplugindocs resource documentation template in the schema section, if the attribute or block is in the...

Hi @ctreatma 👋 Thank you for reporting this and sorry you ran into trouble here. I can reproduce this behavior via: ```shell gh repo clone equinix/terraform-provider-equinix cd terraform-provider-equinix tfplugindocs migrate...

It seems there is conflict/ambiguity between https://github.com/hashicorp/terraform-plugin-docs/?tab=readme-ov-file#conventional-paths and https://developer.hashicorp.com/terraform/registry/providers/docs#navigation-hierarchy, which is unfortunate. For what its worth as a "convention", many of the official and partner tier providers already tend to...