Loading...
Loading...
### Terraform Version ```shell Terraform v1.10.5 on darwin_arm64 (I did check the release notes of the newer versions and didn't spot anything that might be a fix, but happy to be told I missed something) ``` ### Terraform Configuration Files ```terraform module "vpc_endpoints" { source = "cloudposse/vpc/aws//modules/vpc-endpoints" version = "2.2.0" ... ``` ### Debug Output ``` ...debug output, or link to a gist... ``` ### Expected Behavior `2.2.0` should have been installed ### Actual Behavior `v2.2.0` was installed (note the v). The repo maintainer in this case recently pushed `v2.2.0` in addition to the existing `2.2.0`. ### Steps to Reproduce `terraform init` ### Additional Context I haven't really dug into the logic, but it appears that in the `version` field, Terraform will accept values with, or without, a v prefix. However, in this case where there are both, it preferred the v2.2.0 tag which introduced unknown changes into our plans. I understand the `v` handling behaviour if there is only one matching value, but in the case that there are both (`2.2.0 and v2.2.0`), it was confusing that Terraform wasn't using the one that we had declared `2.2.0`. Instead, we had to do something like: ```terraform module "vpc_endpoints" { source = "git::https://github.com/cloudposse/terraform-aws-vpc.git//modules/vpc-endpoints?ref=2.2.0" ... ``` ### References https://github.com/cloudposse/terraform-aws-vpc/issues/160 ### Generative AI / LLM assisted development? _No response_
Click on a version to see all relevant bugs
Terraform Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.