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

Unable to assign private_ip to instance (multiple) #102

Closed
39mbac opened this issue Jun 14, 2019 · 5 comments · Fixed by #103
Closed

Unable to assign private_ip to instance (multiple) #102

39mbac opened this issue Jun 14, 2019 · 5 comments · Fixed by #103

Comments

@39mbac
Copy link

39mbac commented Jun 14, 2019

Using

   private_ip     = “10.10.1.10”

To assign static address to a single instance works great using this module.

I have a need to create multiple instances and statically set their ip’s

  private_ip = [“10.10.1.10”, ‘10.10.2.10”] results in the “got list should be string error”

Have tried setting as variable before module as in below which also does not work

variable “private_ip”  {
                  type = “list”
}

What is the proper way to provision multiple instances and statically assign private_ip?

@antonbabenko
Copy link
Member

You are right, currently, this module creates instances but it is not possible to give each instance a fixed private IP. Sounds like a small pull-request is missing.

@39mbac
Copy link
Author

39mbac commented Jun 14, 2019

Glad I am not missing something. Not sure how to go about properly adding a pull-request ...all guidance appreciated as not having this functionality has me at a temporary standstill. Thanks!

@antonbabenko
Copy link
Member

Fixed in v2.2.0

@39mbac
Copy link
Author

39mbac commented Jun 14, 2019

Wow...that’s service! Is this backwards compatible to TF v11 or is 12 required? As it is v.2.2.0 assume 12 only?

Sebor pushed a commit to Sebor/terraform-aws-ec2-instance that referenced this issue Aug 6, 2020
@github-actions
Copy link

github-actions bot commented Nov 9, 2022

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 9, 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

Successfully merging a pull request may close this issue.

2 participants