Warning/Deprecation Notice at Module Layer

[frugecn]

Terraform Version

1+

Use Cases

Organizations that create modules for teams use for terraform code-sets need some way to indicate deprecation of input variables/output fields of module/modules themselves for their end-users on Init, TF Validate, Plan, Apply similar to existing functionality in the SDKv2 for plug-in development.

Plugin Development - SDKv2 Deprecations, Removals, and Renames Best Practices | Terraform | HashiCorp Developer]

Attempted Solutions

Looking at creating an out of process executable to scan plans to run after execution of one of the plans. If the pre and post conditions in lifecycle have pass or fail with the warning on only the fail condition. Adding warning to the documentation.

Proposal

a couple of ideas:
lifecycle pre/post condition with a warning option
Warning process on variables similar to the exception process
a message sent back from the registry when caching the code from the repo similar to provider deprecation warnings or TF new version available warnings

References

No response

[jbardin]

Duplicate of #5949

[jbardin]

Also, variable deprecation #32594, and output deprecation #18381

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.