regenerate code from updated spec

equinix/services/metalv1/__init__.py

@@ -164,14 +164,11 @@
 from equinix.services.metalv1.models.ip_reservation_request_input import IPReservationRequestInput
 from equinix.services.metalv1.models.instances_batch_create_input import InstancesBatchCreateInput
 from equinix.services.metalv1.models.instances_batch_create_input_batches_inner import InstancesBatchCreateInputBatchesInner
-from equinix.services.metalv1.models.instances_batch_create_input_batches_inner_all_of import InstancesBatchCreateInputBatchesInnerAllOf
 from equinix.services.metalv1.models.interconnection import Interconnection
 from equinix.services.metalv1.models.interconnection_fabric_provider import InterconnectionFabricProvider
 from equinix.services.metalv1.models.interconnection_list import InterconnectionList
-from equinix.services.metalv1.models.interconnection_metro import InterconnectionMetro
 from equinix.services.metalv1.models.interconnection_metro_list import InterconnectionMetroList
 from equinix.services.metalv1.models.interconnection_metro_list_metros_inner import InterconnectionMetroListMetrosInner
-from equinix.services.metalv1.models.interconnection_metro_list_metros_inner_all_of import InterconnectionMetroListMetrosInnerAllOf
 from equinix.services.metalv1.models.interconnection_metro_list_metros_inner_all_of_providers_inner import InterconnectionMetroListMetrosInnerAllOfProvidersInner
 from equinix.services.metalv1.models.interconnection_port import InterconnectionPort
 from equinix.services.metalv1.models.interconnection_port_list import InterconnectionPortList

equinix/services/metalv1/docs/InstancesBatchCreateInputBatchesInner.md

@@ -6,8 +6,8 @@
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
 **hostnames** | **List[str]** |  | [optional] 
-**href** | **str** |  | [optional] 
 **quantity** | **int** | The number of devices to create in this batch. The hostname may contain an `{{index}}` placeholder, which will be replaced with the index of the device in the batch. For example, if the hostname is `device-{{index}}`, the first device in the batch will have the hostname `device-01`, the second device will have the hostname `device-02`, and so on. | [optional] 
+**href** | **str** |  | [optional] 
 **metro** | **str** | Metro code or ID of where the device should be provisioned in, or it can be instructed to create the device in the best available metro with `{ \"metro\": \"any\" }`. The special metro value of any means anywhere, any metro. When any is chosen in the request, the metro location is picked per our scheduling algorithms that favor the following factors: hardware reservation location (if requesting reserved hardware), ip reservations, spot instances, etc. The any keyword *does not* optimize for cost, this means that usage costs (instance, transfer, other features dependent on location) will vary. Please check metro value in response to see where the device was created. Either metro or facility must be provided. | 
 **always_pxe** | **bool** | When true, devices with a `custom_ipxe` OS will always boot to iPXE. The default setting of false ensures that iPXE will be used on only the first boot. | [optional] 
 **billing_cycle** | **str** | The billing cycle of the device. | [optional] 
@@ -16,7 +16,7 @@ Name | Type | Description | Notes
 **features** | **List[str]** | The features attribute allows you to optionally specify what features your server should have.  In the API shorthand syntax, all features listed are `required`:  ``` { \"features\": [\"tpm\"] } ```  Alternatively, if you do not require a certain feature, but would prefer to be assigned a server with that feature if there are any available, you may specify that feature with a `preferred` value. The request will not fail if we have no servers with that feature in our inventory. The API offers an alternative syntax for mixing preferred and required features:  ``` { \"features\": { \"tpm\": \"required\", \"raid\": \"preferred\" } } ```  The request will only fail if there are no available servers matching the required `tpm` criteria. | [optional] 
 **hardware_reservation_id** | **str** | The Hardware Reservation UUID to provision. Alternatively, `next-available` can be specified to select from any of the available hardware reservations. An error will be returned if the requested reservation option is not available.  See [Reserved Hardware](https://deploy.equinix.com/developers/docs/metal/deploy/reserved/) for more details. | [optional] 
 **hostname** | **str** | The hostname to use within the operating system. The same hostname may be used on multiple devices within a project. | [optional] 
-**ip_addresses** | [**List[IPAddress]**](IPAddress.md) | The `ip_addresses attribute will allow you to specify the addresses you want created with your device.  The default value configures public IPv4, public IPv6, and private IPv4.  Private IPv4 address is required. When specifying `ip_addresses`, one of the array items must enable private IPv4.  Some operating systems require public IPv4 address. In those cases you will receive an error message if public IPv4 is not enabled.  For example, to only configure your server with a private IPv4 address, you can send `{ \"ip_addresses\": [{ \"address_family\": 4, \"public\": false }] }`.  It is possible to request a subnet size larger than a `/30` by assigning addresses using the UUID(s) of ip_reservations in your project.  For example, `{ \"ip_addresses\": [..., {\"address_family\": 4, \"public\": true, \"ip_reservations\": [\"uuid1\", \"uuid2\"]}] }`  To access a server without public IPs, you can use our Out-of-Band console access (SOS) or proxy through another server in the project with public IPs enabled. | [optional] [default to [{address_family=4, public=true}, {address_family=4, public=false}, {address_family=6, public=true}]]
+**ip_addresses** | [**List[IPAddress]**](IPAddress.md) | The `ip_addresses attribute will allow you to specify the addresses you want created with your device.  The default value configures public IPv4, public IPv6, and private IPv4.  Private IPv4 address is required. When specifying `ip_addresses`, one of the array items must enable private IPv4.  Some operating systems require public IPv4 address. In those cases you will receive an error message if public IPv4 is not enabled.  For example, to only configure your server with a private IPv4 address, you can send `{ \"ip_addresses\": [{ \"address_family\": 4, \"public\": false }] }`.  It is possible to request a subnet size larger than a `/30` by assigning addresses using the UUID(s) of ip_reservations in your project.  For example, `{ \"ip_addresses\": [..., {\"address_family\": 4, \"public\": true, \"ip_reservations\": [\"uuid1\", \"uuid2\"]}] }`  To access a server without public IPs, you can use our Out-of-Band console access (SOS) or proxy through another server in the project with public IPs enabled. | [optional] [default to [{"address_family":4,"public":true},{"address_family":4,"public":false},{"address_family":6,"public":true}]]
 **ipxe_script_url** | **str** | When set, the device will chainload an iPXE Script at boot fetched from the supplied URL.  See [Custom iPXE](https://deploy.equinix.com/developers/docs/metal/operating-systems/custom-ipxe/) for more details. | [optional] 
 **locked** | **bool** | Whether the device should be locked, preventing accidental deletion. | [optional] [default to False]
 **network_frozen** | **bool** | If true, this instance can not be converted to a different network type. | [optional] 

equinix/services/metalv1/docs/Interconnection.md

@@ -13,7 +13,7 @@ Name | Type | Description | Notes
 **facility** | [**Facility**](Facility.md) |  | [optional] 
 **href** | **str** |  | [optional] 
 **id** | **str** |  | [optional] 
-**metro** | [**InterconnectionMetro**](InterconnectionMetro.md) |  | [optional] 
+**metro** | [**Metro**](Metro.md) | The location of where the shared or Dedicated Port is located. For interconnections with Dedicated Ports,   this will be the location of the Dedicated Ports. For Fabric VCs (Metal Billed), this is where interconnection will be originating from, as we pre-authorize the use of one of our shared ports   as the origin of the interconnection using A-Side service tokens. We only allow local connections for Fabric VCs (Metal Billed), so the destination location must be the same as the origin. For Fabric VCs (Fabric Billed),    this will be the destination of the interconnection. We allow remote connections for Fabric VCs (Fabric Billed), so the origin of the interconnection can be a different metro set here. | [optional] 
 **mode** | **str** | The mode of the interconnection (only relevant to Dedicated Ports). Shared connections won't have this field. Can be either 'standard' or 'tunnel'.   The default mode of an interconnection on a Dedicated Port is 'standard'. The mode can only be changed when there are no associated virtual circuits on the interconnection.   In tunnel mode, an 802.1q tunnel is added to a port to send/receive double tagged packets from server instances. | [optional] 
 **name** | **str** |  | [optional] 
 **organization** | [**Organization**](Organization.md) |  | [optional] 

equinix/services/metalv1/models/__init__.py

@@ -108,14 +108,11 @@
 from equinix.services.metalv1.models.ip_reservation_request_input import IPReservationRequestInput
 from equinix.services.metalv1.models.instances_batch_create_input import InstancesBatchCreateInput
 from equinix.services.metalv1.models.instances_batch_create_input_batches_inner import InstancesBatchCreateInputBatchesInner
-from equinix.services.metalv1.models.instances_batch_create_input_batches_inner_all_of import InstancesBatchCreateInputBatchesInnerAllOf
 from equinix.services.metalv1.models.interconnection import Interconnection
 from equinix.services.metalv1.models.interconnection_fabric_provider import InterconnectionFabricProvider
 from equinix.services.metalv1.models.interconnection_list import InterconnectionList
-from equinix.services.metalv1.models.interconnection_metro import InterconnectionMetro
 from equinix.services.metalv1.models.interconnection_metro_list import InterconnectionMetroList
 from equinix.services.metalv1.models.interconnection_metro_list_metros_inner import InterconnectionMetroListMetrosInner
-from equinix.services.metalv1.models.interconnection_metro_list_metros_inner_all_of import InterconnectionMetroListMetrosInnerAllOf
 from equinix.services.metalv1.models.interconnection_metro_list_metros_inner_all_of_providers_inner import InterconnectionMetroListMetrosInnerAllOfProvidersInner
 from equinix.services.metalv1.models.interconnection_port import InterconnectionPort
 from equinix.services.metalv1.models.interconnection_port_list import InterconnectionPortList