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

Change "count" variable name to permit future Terraform feature? #23

Closed
apparentlymart opened this issue Mar 5, 2018 · 2 comments
Closed

Comments

@apparentlymart
Copy link
Contributor

Hello!

This module defines a variable called count:

variable "count" {
description = "Number of instances to launch"
default = 1
}

This is valid in current Terraform, but to implement hashicorp/terraform#953 will require this variable name to be reserved. We're currently hoping to make this name, along with for_each and lifecycle, reserved names that cannot be used for modules in preparation for them getting special meaning in a later release where that issue is implemented.

Would you be open to changing this variable name to be instance_count instead? Although we are not planning to implement count for modules immediately, we'd like to begin a deprecation cycle for use of this name as a variable so that the name is free for a change in a later release.

I noticed that terraform-aws-modules/rds/aws and terraform-aws-modules/elb/aws also have variables called count, for which I'd ask a similar question, but I didn't want to spam with loads of issues about the same thing.

Thanks!

@antonbabenko
Copy link
Member

Martin, thanks for heads up!

antonbabenko added a commit that referenced this issue Mar 6, 2018
Renamed count to instance_count (fixes #23)
Sebor pushed a commit to Sebor/terraform-aws-ec2-instance that referenced this issue Aug 6, 2020
Sebor pushed a commit to Sebor/terraform-aws-ec2-instance that referenced this issue Aug 6, 2020
…s/renamed-count

Renamed count to instance_count (fixes terraform-aws-modules#23)
@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 10, 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