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

[BUG] - VPC 2.0 bind order not respected #550

Open
quantimnot opened this issue Feb 3, 2025 · 0 comments · May be fixed by #551
Open

[BUG] - VPC 2.0 bind order not respected #550

quantimnot opened this issue Feb 3, 2025 · 0 comments · May be fixed by #551
Labels

Comments

@quantimnot
Copy link

I want VPC interfaces attached to my instances in a deterministic manner.

Currently, it doesn't matter in what order I define them:

vpc2_ids = [vultr_vpc2.data.id, vultr_vpc2.control.id]

and

vpc2_ids = [vultr_vpc2.control.id, vultr_vpc2.data.id]

always result in this attachment order: [vultr_vpc2.data.id, vultr_vpc2.control.id]

The VPC creation order doesn't affect the binding order either.

So, currently, if I wanted to use an automated setup, I would either need to write a program on the VPS node to examine the assigned IP, so that I can config the correct interface (which is stupid), or do it manually (which is stupid).

@quantimnot quantimnot added the bug label Feb 3, 2025
@quantimnot quantimnot linked a pull request Feb 3, 2025 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant