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

Expose MACs of private networks in instance resource #54

Closed
mlazowik opened this issue Nov 22, 2018 · 3 comments
Closed

Expose MACs of private networks in instance resource #54

mlazowik opened this issue Nov 22, 2018 · 3 comments

Comments

@mlazowik
Copy link
Contributor

Around here: https://github.com/squat/terraform-provider-vultr/blob/master/vultr/resource_instance.go#L276

The question is how to do this without breaking the API? Right know each private network value is just its IP, switching this to an object would mean existing configs ppl have wouldn't work.

@mlazowik mlazowik changed the title MACs of private networks in instance resource Expose MACs of private networks in instance resource Nov 22, 2018
@mlazowik
Copy link
Contributor Author

A separate private_networks_with_mac key? The name is clunky, but I can't come up with anything better.

@squat
Copy link
Owner

squat commented Nov 24, 2018

@mlazowik it’s unfortunate, but it’s ok to introduce a breaking API change. The API is not yet stable and this is exactly the right time to be introducing new features that help make this provider a fully featured plugin that is useful for all scenarios. If you’d like to have a go at writing the new feature, I would be more than happy to review it :)

@mlazowik
Copy link
Contributor Author

mlazowik commented Nov 24, 2018

Sure, I'll take a stab at that. I wonder how the state file will react to this, it should auto update on next apply (because it does refresh before apply), right?

mlazowik added a commit to qedsoftware/terraform-provider-vultr that referenced this issue Dec 5, 2018
Terraform will support nested maps starting with 0.12 (late summer),
so I'm adding a separate map of MACs.

https://www.hashicorp.com/blog/terraform-0-12-rich-value-types

Fixes squat#54
mlazowik added a commit to qedsoftware/terraform-provider-vultr that referenced this issue Dec 5, 2018
Terraform will support nested maps starting with 0.12 (late summer),
so I'm adding a separate map of MACs.

https://www.hashicorp.com/blog/terraform-0-12-rich-value-types

Fixes squat#54
mlazowik added a commit to qedsoftware/terraform-provider-vultr that referenced this issue Dec 5, 2018
Terraform will support nested maps starting with 0.12 (late summer),
so I'm adding a separate map of MACs.

https://www.hashicorp.com/blog/terraform-0-12-rich-value-types

Fixes squat#54
mlazowik added a commit to qedsoftware/terraform-provider-vultr that referenced this issue Dec 28, 2018
Terraform will support nested maps starting with 0.12 (late summer),
so I'm adding a separate map of MACs.

https://www.hashicorp.com/blog/terraform-0-12-rich-value-types

Fixes squat#54
squat pushed a commit to qedsoftware/terraform-provider-vultr that referenced this issue Jan 8, 2019
Terraform will support nested maps starting with 0.12 (late summer),
so I'm adding a separate map of MACs.

https://www.hashicorp.com/blog/terraform-0-12-rich-value-types

Fixes squat#54
@squat squat closed this as completed in #55 Jan 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants