Skip to content
This repository has been archived by the owner on Feb 11, 2022. It is now read-only.

Abstract Network Interface Order #22

Open
codygreen opened this issue Oct 8, 2019 · 1 comment
Open

Abstract Network Interface Order #22

codygreen opened this issue Oct 8, 2019 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@codygreen
Copy link
Member

Currently, the EC2 network interfaces are assigned statically via:

  • 0:mgmt
  • 1:public
  • 2:internal

This would cause a problem if you tried to use the vpc_mgmt_subnet_ids and vpc_private_subnet_ids variables to create a BIG-IP.

Ideally, we would abstract this so you can create a 2 nic deployment without statically assigning the 2nd nic to the vpc_public_subnet_ids.

@codygreen codygreen added the enhancement New feature or request label Oct 8, 2019
@codygreen
Copy link
Member Author

refactored NIC creation to address this issue

@codygreen codygreen mentioned this issue Apr 1, 2020
@codygreen codygreen self-assigned this Apr 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant