Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] private_networking depricated and insufficient for DigitalOcean salt-cloud interface #63714

Closed
waynegemmell opened this issue Feb 14, 2023 · 0 comments · Fixed by #63745
Labels
Bug broken, incorrect, or confusing behavior needs-triage Salt-Cloud

Comments

@waynegemmell
Copy link
Contributor

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.

image
https://docs.digitalocean.com/reference/api/kafka-beta-api-reference/#operation/droplets_create

@waynegemmell waynegemmell added Bug broken, incorrect, or confusing behavior needs-triage labels Feb 14, 2023
@waynegemmell waynegemmell mentioned this issue Feb 20, 2023
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior needs-triage Salt-Cloud
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants