docs/PrivateNetworkConfiguration.md in pnap_bmc_api-1.0.0 vs docs/PrivateNetworkConfiguration.md in pnap_bmc_api-1.1.0
- old
+ new
@@ -2,10 +2,10 @@
## Properties
| Name | Type | Description | Notes |
| ---- | ---- | ----------- | ----- |
-| **gateway_address** | **String** | The address of the gateway assigned / to assign to the server. It'll be null and won't be displayed as part of response body if server is a member of both public and private networks. When used as part of request body, it has to match one of the IP addresses used in the existing assigned private networks for the relevant location. Also, this field can be submitted only when provisioning a server without being a member of any public network. | [optional] |
+| **gateway_address** | **String** | The address of the gateway assigned / to assign to the server. When used as part of request body, it has to match one of the IP addresses used in the existing assigned private networks for the relevant location. Deprecated in favour of a common gateway address across all networks available under NetworkConfiguration. | [optional] |
| **configuration_type** | **String** | Determines the approach for configuring private network(s) for the server being provisioned. Currently this field should be set to `USE_OR_CREATE_DEFAULT` or `USER_DEFINED`. | [optional][default to 'USE_OR_CREATE_DEFAULT'] |
| **private_networks** | [**Array<ServerPrivateNetwork>**](ServerPrivateNetwork.md) | The list of private networks this server is member of. When this field is part of request body, it'll be used to specify the private networks to assign to this server upon provisioning. Used alongside the `USER_DEFINED` configurationType. | [optional] |
## Example