metal_device_network_type

[t0mk]

Create module for metal_device_network_type.

Analogical to resource equinix_metal_device_network_type in terraform-provider-equinix:

• https://registry.terraform.io/providers/equinix/equinix/latest/docs/resources/equinix_metal_device_network_type
• https://github.com/equinix/terraform-provider-equinix/tree/master/equinix/resource_metal_device_network_type.go

Module should

• be in plugins/modules/metal_device_network_type.py
• follow development conventions
• be idempotent
• support check_mode if it's an _info module
• have doc fields for (ansible-specdoc)[https://github.com/linode/ansible-specdoc] (see metal_project.py for an example
  • module_spec
  • specdoc_example
  • result_sample
  • SPECDOC_METAL
  • (DOCUMENATION, EXAMPLES and RETURN will be generated by make docs)
• have an integration test in tests/integration/targets/metal_device_network_type/tasks/main.yml
• (semi-optional) pass sanity test:
  $ cd .ansible/collections/ansible_collections/equinix/cloud
$ ansible-test sanity -v --docker --python 3.10 metal_device_network_type.py

See the newest added module to get an idea how to do implement this.

[displague]

This is a Terraform-ism that we potentially don't need if the ports are made to be configurable in the Metal Device.