Repository navigation
sshInterfaceId for primary and secondary device in self configured devices - #3
Conversation
…igured scenario when creating devices
| InterfaceCount *int `json:"interfaceCount,omitempty"` | ||
| Core *DeviceCoreInformation `json:"core,omitempty"` | ||
| DeviceManagementType *string `json:"deviceManagementType,omitempty"` | ||
| SshInterfaceId *string `json:"sshInterfaceId,omitempty"` |
There was a problem hiding this comment.
There was a problem hiding this comment.
Hi Marques, this field is a string in API. For some reasons, it is an integer in the documentation. We are going to make the changes in swagger. In the payload of the documentation(the first link in your response), it's actually a string instead of integer. We will ask team to update it to be string.
There was a problem hiding this comment.
In the spec, this is currently a value such as: 4. Why should it be a string? It seems an int would be the appropriate type unless other formats can be returned or set.
sshInterfaceId:
type: integer
example: 4
description: You may specify any available interface on the device as the sshInterfaceId. This field is only applicable to self-configured devices.
There was a problem hiding this comment.
We are updating the specs to change it to string. There is a possibility of sub-interfaces. In that case, we might use '-' or '.' to represent interface id
…ption when providing sshInterfaceId for equinix managed device
Add sshInterfaceId for both primary and secondary device in self configured scenario when creating devices
Needed for equinix/terraform-provider-equinix#58