Launch droplet in a specific project #175
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request adds support for specifying a DigitalOcean Project ID when creating droplets with the DigitalOcean builder. This allows users to launch droplets directly into a specific DigitalOcean project, improving resource organization and management. The changes include updates to the configuration structs, documentation, and droplet creation logic.
DigitalOcean Project ID support:
project_idfield to the DigitalOcean builder configuration (ConfigandFlatConfigstructs inconfig.goandconfig.hcl2spec.go). [1] [2]project_idas a valid configuration key.project_idwhen launching a new droplet and to store it in the build state. (step_create_droplet.go) [1] [2]Documentation updates:
project_idto the documented list of available configuration keys in both the main README and partial documentation files. (README.md,Config-not-required.mdx) [1] [2]Depends on: digitalocean/godo#881
Closes #174