Terraform init downloading wrong aws provider version

Naragorn commented 4 years ago

Terraform Version

0.13.0

Terraform Configuration Files

terraform { required_version = "0.13" required_providers { aws = "3.0" } }

Debug Output

Crash Output

Initializing modules...

bootstrap in ../../../solutions/bootstrap
bootstrap.codebuild_terraform_apply in ../../../modules/codebuild
bootstrap.codebuild_terraform_plan in ../../../modules/codebuild
bootstrap.terraform_codepipeline_artifacts_store in ../../../modules/s3_bucket
bootstrap.terraform_logging_bucket in ../../../modules/s3_bucket
bootstrap.terraform_pipeline in ../../../modules/codepipeline
data-repository in ../../../modules/s3_bucket
lambda_functions in ../../../solutions/lambda
lambda_functions.create_model in ../../../modules/lambda
lambda_functions.get_endpoint_status in ../../../modules/lambda
lambda_functions.get_model_results in ../../../modules/lambda
lambda_functions.get_sagemaker_names in ../../../modules/lambda
lambda_functions.model_proxy in ../../../modules/lambda
lambda_functions.test_sagemaker_endpoints in ../../../modules/lambda
mlops_pipeline in ../../../solutions/mlops_pipeline
mlops_pipeline.mlops_artifact_bucket in ../../../modules/s3_bucket
mlops_pipeline.mlops_deploy_dev in ../../../modules/stepfunctions
mlops_pipeline.mlops_deploy_prod in ../../../modules/stepfunctions
mlops_pipeline.mlops_deploy_test in ../../../modules/stepfunctions
mlops_pipeline.mlops_testing_dev in ../../../modules/stepfunctions
mlops_pipeline.mlops_testing_test in ../../../modules/stepfunctions
mlops_pipeline.mlops_training in ../../../modules/stepfunctions
model-repository in ../../../modules/s3_bucket
sagemaker_notebook in ../../../modules/sagemaker
terraform_state in ../../../solutions/tf_state
vpc_network in ../../../modules/vpc

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically use this backend unless the backend configuration changes.

Initializing provider plugins...

Finding latest version of hashicorp/archive...
Finding latest version of -/aws...
Finding hashicorp/aws versions matching "3.0.*"...
Installing hashicorp/archive v1.3.0...
Installed hashicorp/archive v1.3.0 (signed by HashiCorp)
Installing -/aws v3.3.0...
Installed -/aws v3.3.0 (signed by HashiCorp)
Installing hashicorp/aws v3.0.0...
Installed hashicorp/aws v3.0.0 (signed by HashiCorp)

The following providers do not have any version constraints in configuration, so the latest version was installed.

To prevent automatic upgrades to new major versions that may contain breaking changes, we recommend adding version constraints in a required_providers block in your configuration, with the constraint strings suggested below.

-/aws: version = "~> 3.3.0"
hashicorp/archive: version = "~> 1.3.0"

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see any changes that are required for your infrastructure. All Terraform commands should now work.

If you ever set or change modules or backend configuration for Terraform, rerun this command to reinitialize your working directory. If you forget, other commands will detect it and remind you to do so if necessary.

Expected Behavior

Terraform would install and use provider -/aws 3.0

Actual Behavior

Terraform will install and use provider -/aws 3.3, which breaks my code

Steps to Reproduce

terraform { required_version = "0.13" required_providers { aws = "3.0" } }

then run:

terraform init

Additional Context

References

Naragorn commented 4 years ago

Sorry I just saw this is a duplicate of https://github.com/hashicorp/terraform/issues/25819

ghost commented 3 years ago

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

hashicorp / terraform