How do you specify a module's version when publishing it to the public Terraform Module Registry?
How do you specify a module's version when publishing it to the public Terraform Module Registry?
When publishing a module to the Terraform Module Registry, the module's version is typically specified using release tags in the associated repository. Release tag names must follow semantic versioning (e.g., v1.0.4 or 0.9.2). These tags help the registry to identify and manage different versions of the module.
The registry uses tags to identify module versions. Release tag names must be a semantic version, which can optionally be prefixed with a v . For example, v1. 0.4 and 0.9.
https://www.terraform.io/registry/modules/publish
x.y.z tags for releases. The registry uses tags to identify module versions. Release tag names must be a semantic version, which can optionally be prefixed with a v. For example, v1.0.4 and 0.9.2. To publish a module initially, at least one release tag must be present. Tags that don't look like version numbers are ignored. ANSWER C
answer is C: Once a module is published, you can release a new version of a module by simply pushing a properly formed Git tag. x.y.z tags for releases. The registry uses tags to identify module versions. Release tag names must be a semantic version, which can optionally be prefixed with a v. For example, v1.0.4 and 0.9.2. To publish a module initially, at least one release tag must be present. Tags that don't look like version numbers are ignored. https://developer.hashicorp.com/terraform/registry/modules/publish
C makes sense to me
A module's version is specified using the release tag names. So, the right answer is C.
C. The release tags in the associated repo. When publishing a module to the Terraform Module Registry, the module version is typically specified using Git tags in the associated Git repository. Terraform retrieves the module from the registry using the provider's source argument, which includes the module's owner, name, and version. By specifying the version in the source argument of your module, Terraform will download that specific version of the module from the registry.
C is the correct answer.