Enhancement request: Enhance Droplet Create API to also take project id

[Utsavk]

I have not found the option for mentioning project id in create droplet API. As per my understanding, a created droplet is first assigned to the default project and then another API call is required for assigning it to the desired project. This can be optimized by accepting the project id as an optional input parameter of create API. I would like to contribute for this.

[ChiefMateStarbuck]

Per my comment, we at DO are planning how best to execute this feature. We will update the you and larger community as soon as more details become available.

[Zarquan]

Not just for droplets. Ideally we would like to be able to use --project when creating things like Kubernetes clusters, load balancers etc. .. anything really.

[Zarquan]

You don't need to change the server side REST API. This could be wrapped up in the doctl client. Resources could be created in the default project as now, but if the --project option is specified the doctl client makes the extra call to move the resource to the specified project.

[arnav13081994]

This would be a great addition

[amoralesc]

Commenting here to cross-reference that the latest doctl release finally added a --project-id flag when creating a project. The specific issue is here.