Semantically duplicated tags

[goruha]

Describe the Bug

There are semantically equivalent version tags that point to different commits

• 0.1.0 and v0.1.0
• 0.1.1 and v0.1.1
• 0.1.2 and v0.1.2

Terraform registry uses the latest tag in case of having a semantically equal tag, which causes an inconsistency reference module with the git URI and the Terraform registry.

Expected Behavior

The tagged module version is what is installed by Terraform

Steps to Reproduce

module "example" {
  source = "git::https://github.com/cloudposse/terraform-aws-cloudtrail-cloudwatch-alarms.git?ref=0.1.0" 
  ...

module "example" {
  source = "git::https://github.com/cloudposse/terraform-aws-cloudtrail-cloudwatch-alarms.git?ref=v0.1.0" 
  ...

module "example" {
  source  = "cloudposse/cloudtrail-cloudwatch-alarms/aws"
  version = "0.1.0"  ...

Should point to the same code

Screenshots

No response

Environment

No response

Additional Context

No response

[goruha]

Around a year ago, we standardized our release process and versioning.
Now

• we always use v prefixed versions
• all releases are created automatically.
• tags and releases are immutable
• none of the developers or maintainers can create/update/delete tags or releases

All of that gives us confidence that we would not have the same issue in the future.

After you raised the ticket, we checked all our Terraform components and modules.
We reviewed 185 Terraform modules and 170 Terraform components. Out of those, we found only 4 cases of semantically duplicated tags pointing to different commits. All of them, except cloudposse/terraform-aws-vpc@2.2.0, are significantly behind the latest versions in history (more than a year ago).

As a solution, we removed older semantically duplicated tags to reconcile what we have in git with how the Terraform registry handles those cases.

For the cloudposse/terraform-aws-cloudtrail-cloudwatch-alarms, we removed tags

• v0.1.0
• 0.1.1
• v0.1.2

[goruha]

Reference cloudposse/terraform-aws-vpc#160