Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warnings on upgrading to Terraform v0.11.1 #31

Closed
horsey opened this issue Dec 7, 2017 · 7 comments
Closed

Warnings on upgrading to Terraform v0.11.1 #31

horsey opened this issue Dec 7, 2017 · 7 comments

Comments

@horsey
Copy link

horsey commented Dec 7, 2017




Warning: output "this_db_parameter_group_arn": must use splat syntax to access aws_db_parameter_group.this attribute "arn", because it has "count" set; use aws_db_parameter_group.this.*.arn to obtain a list of the attributes across all instances
@horsey horsey changed the title Warnings on upgrading to Terraform vTerraform v0.11.1 Warnings on upgrading to Terraform v0.11.1 Dec 7, 2017
@antonbabenko
Copy link
Member

Thanks for reporting! This is an important issue to fix in this and several other AWS modules also.

@horsey
Copy link
Author

horsey commented Dec 7, 2017

Probably not related to this issue, but is there a way to pin my infrastructure to a version of the module? I happen to delete my .terraform directory and discovered that I needed to upgrade my Terraform version because it was not compatible with the latest version of the module.

@antonbabenko
Copy link
Member

Yes, you can specify version like this:

module "db" {
  source = "terraform-aws-modules/rds/aws"
  version = "v1.4.0"

  # the rest of arguments...
}

Here you can see all releases - https://github.com/terraform-aws-modules/terraform-aws-rds/releases

@horsey
Copy link
Author

horsey commented Dec 7, 2017

Thank you!

@horsey
Copy link
Author

horsey commented Dec 7, 2017

@antonbabenko Any plans to make a release with the fix?

Thanks in advance.

@antonbabenko
Copy link
Member

This is now fixed in v1.5.0

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants