You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
The Digialocean APT has depricated the private_networking option when creating a new droplet. It needs to be replaced with the vpc_uuid field in order to target which vpc you wish to attach to the droplet that's being created.
This is fairly important as you can have multiple VPC's (Virtual Private Cloud) setup per data center but you can only attach one VPC to each droplet and as such you need to request the appropriate one. This is not transferable so cannot get rectified at a later stage.
The image below indicates the update from the documentation and below that the url points to the documentation.
Description
The Digialocean APT has depricated the private_networking option when creating a new droplet. It needs to be replaced with the vpc_uuid field in order to target which vpc you wish to attach to the droplet that's being created.
This is fairly important as you can have multiple VPC's (Virtual Private Cloud) setup per data center but you can only attach one VPC to each droplet and as such you need to request the appropriate one. This is not transferable so cannot get rectified at a later stage.
The image below indicates the update from the documentation and below that the url points to the documentation.
https://docs.digitalocean.com/reference/api/kafka-beta-api-reference/#operation/droplets_create
The text was updated successfully, but these errors were encountered: