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

Request: Add support for promiscuous NICs #68

Open
dcode opened this issue Jul 9, 2020 · 0 comments
Open

Request: Add support for promiscuous NICs #68

dcode opened this issue Jul 9, 2020 · 0 comments

Comments

@dcode
Copy link

dcode commented Jul 9, 2020

Terraform Version

Terraform v0.12.26

Affected Resource(s)

Please list the resources as a list, for example:

  • skytap_vm

Terraform Configuration Files

Proposed feature:

# From the documentation example
resource "skytap_vm" "vm" {
  template_id = 1473407
  vm_id = 37865463
  environment_id = "${skytap_environment.environment.id}"
  name = "my vm"
  cpus = 2
  ram = 4096

  os_disk_size = 40000

  network_interface  {
     interface_type = "vmxnet3"
     network_id = "${skytap_network.network.id}"
     ip = "172.128.0.1"
     hostname = "myhost"
     promiscuous = true

    published_service {
      name = "ssh"
      internal_port = 22
    }
  }
}

Debug Output

n/a

Panic Output

n/a

Expected Behavior

I expected that I would be able to set the promiscuous flag on a given network interface.

Actual Behavior

The documentation didn't suggest any such flag was available.

Steps to Reproduce

  1. Create a terraform file that creates a VM in an environment that you want to have promiscuous mode (my use-case is a nested hypervisor and the feature is available on my account.)
  2. Read the documentation.
  3. Feel sad that I have to manually do this step later.

References

Not a GitHub issue, but this flag is straight out of the SkyTap API Network Adapter v2 resource model

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

1 participant