Closed Lukasz-Equinix closed 1 month ago
When using reserved hardware the api https://github.com/equinix-labs/ansible-collection-equinix/blob/55bc3d1b645a859b7b3c93309cf5b264d23a4976/plugins/modules/metal_device.py#L373 says you can provide next-available instead of the device uuid, but currently this is still checked against the uuid regex and the exception is thrown https://github.com/equinix-labs/ansible-collection-equinix/blob/55bc3d1b645a859b7b3c93309cf5b264d23a4976/plugins/module_utils/equinix.py#L110
next-available
Skipping the uuid check if this is the case.
This PR is included in version 0.6.1 :tada:
When using reserved hardware the api https://github.com/equinix-labs/ansible-collection-equinix/blob/55bc3d1b645a859b7b3c93309cf5b264d23a4976/plugins/modules/metal_device.py#L373 says you can provide
next-available
instead of the device uuid, but currently this is still checked against the uuid regex and the exception is thrown https://github.com/equinix-labs/ansible-collection-equinix/blob/55bc3d1b645a859b7b3c93309cf5b264d23a4976/plugins/module_utils/equinix.py#L110Skipping the uuid check if this is the case.