Consider Migrating Some/All Validators into terraform-plugin-framework

[bflad]

Terraform CLI and Framework Versions

Any Terraform CLI and terraform-plugin-framework version.

Use Cases or Problem Statement

We had separated out this Go module originally because we were not sure how the ecosystem would evolve with all the new framework validation concepts, since we really wanted developers to use custom types when possible, and wanted to leave the room for separate versioning of these declarative validators. Over a year after the framework v1.0.0 release now though, this validators Go module has been surprisingly stable. To prevent future developers from needing to discover and include this Go module as a separate dependency, the validators can be implemented directly in the terraform-plugin-framework Go module.

Proposal

The general process would be:

• Introduce new validator packages and implementations in terraform-plugin-framework containing functionality from this Go module. Update all Go and website documentation to point to the now-native validator implementations. If this proposal is accepted, a feature request issue would be created in terraform-plugin-framework to discuss these details.
• Add Deprecated: Go documentation to all exported functionality in this Go module and a big deprecation changelog
• Cut a release
• Archive the repository and celebrate this fun milestone 🎉

Caveats that can be discussed in this issue:

• It is unclear whether all the existing validators should move over as-is because another option we do have in some of these cases is introducing very common use case validations into the framework base types themselves. e.g. basetypes.StringType{RegularExpression: ...}
• Whether naming of some existing validators would be adjusted, as they would now more "permanent" due to compatibility concerns.
• Whether the implementation details of some existing validators would be adjusted, as they would now be more permanent (potentially be testing those changes in this Go module first).

Additional Information

No response

Code of Conduct

• I agree to follow this project's Code of Conduct