Where are versioning signals for a module published when using the public Terraform Module Registry?

Where are versioning signals for a module published when using the public Terraform Module Registry?

• A. The module's configuration page
• B. Release tags in associated repo
• C. The Terraform code
• D. Registry version field

Answer: (B)

Versioning signals for a module published to the public Terraform Module Registry come from release tags in the module’s source repository. When you create a new release, you add semantic-version git tags (for example, v1.2.0) in the module’s Git repository. The Registry reads these tags and presents them as the available versions for users to pin or reference. The actual Terraform code and the module’s configuration page don’t serve as version indicators to the Registry, and there isn’t a separate manual “registry version” field to fill. So the release tags in the associated repository are the source of the versioning signals.

Versioning signals for a module published to the public Terraform Module Registry come from release tags in the module’s source repository. When you create a new release, you add semantic-version git tags (for example, v1.2.0) in the module’s Git repository. The Registry reads these tags and presents them as the available versions for users to pin or reference. The actual Terraform code and the module’s configuration page don’t serve as version indicators to the Registry, and there isn’t a separate manual “registry version” field to fill. So the release tags in the associated repository are the source of the versioning signals.