Terraform Module Registry incorrectly shows Inputs as required if default = null

[JustinGrote]

See my module for example:
https://registry.terraform.io/modules/JustinGrote/azure-function-powershell/azurerm/

azure_active_directory_id is default=null, so it is an optional variable, but shows as required on the registry.

[mildwonkey]

Thanks for reporting this, @JustinGrote !

Your 0.2.1 link did not work for me but these did:

https://registry.terraform.io/modules/JustinGrote/azure-function-powershell/azurerm/0.2.2?tab=inputs
https://github.com/JustinGrote/terraform-azurerm-azure-function-powershell/blob/master/variables.tf#L61-L65

At a glance, it looks like the registry does not distinguish nil variables (no default) from variables intentionally set to null when determining if a variable is required.

[antonbabenko]

Same here - https://registry.terraform.io/modules/terraform-aws-modules/vpc/aws/2.21.0?tab=inputs as reported in terraform-aws-vpc issue.

Do you have any updates on when this will be fixed, @mildwonkey ?

[weibeld]

Same for the official consul module. Four variables are shown as required on the Terraform Registry page, even though all of them are optional as shown in variables.tf.

This is confusing for potential users of a module, so I hope it will get fixed soon!

[antonbabenko]

Sorry to bother but this is a very frustrating issue for many new users of the modules (I hear this rather often).

Is there any way to give this issue a higher priority?