-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
provider/digitalocean: adds a volume resource #7560
provider/digitalocean: adds a volume resource #7560
Conversation
Hi @aybabtme! Thanks for this, the code looks good. However, running the acceptance test I'm seeing 404s on volumes. Is this something that accounts need configuring for, or is there some kind of eventual consistency we need to take into account for import? For example:
|
Hi @jen20, the The test output goes like:
|
Ah, thanks. Is there a good place to email the account ID to, or are they not considered sensitive? This LGTM - the last thing it needs is a docs page - might be worth noting the beta flag until it's rolled out to everyone? Thanks! |
I just merged the P. |
@stack72 I just rebased, PTAL =] |
@jen20 shoot me an email with your user ID at |
Hi @aybabtme Thanks for letting us know this is GA - just ran the tests on my own account and got the following:
Love that you even included an import :) Merging now! Paul |
* provider/digitalocean: add support for volumes * provider/digitalocean: add documentation for volume resource
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
We're currently in beta with a block storage feature we call "volumes". This adds support for
volume
resources in the DigitalOcean provider.Usage looks like:
To support this, I had to bump the vendored
digitalocean/godo
package. If this results in too much diff noise, I'm happy to send the bump in a separate PR.cc @nickvanw @jphines @rafaelrosafu @neurodrone @ralfonso