-
Notifications
You must be signed in to change notification settings - Fork 398
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
Tag droplet returns 404 error #107
Comments
The tag is required to exist before tagging a resource. |
@bryanl oh! thanks - didn't really know how tagging worked, was just testing, tags aren't visible in the control panel (yet?) anyways. |
@zubfatal Right. There are plans to expose them in the control panel, but currently they are API only. You can find out more here: |
@andrewsomething Thanks - yeah i found that link as well, and I can see how it can be useful if you have a bunch of doplets, not sure how it visually would be the best way to group/display the droplets by tag, but I can see the potential in using tags, could be someting like:
Although that would probably be a bit weird grouping if a droplet has both tags.. Do you know if there is a roadmap or something like that, for stuff Digital Ocean is planning to add? (features for droplets, or changes in the control panel, new datacentre or whatever) |
We don't have a full public roadmap, but we do use UserVoice to track feature requests: https://digitalocean.uservoice.com |
@andrewsomething Cool! thanks - maybe that should be referenced somewhere on the website and/or the control panel? :) |
Running the command:
doctl compute droplet tag <droplet-name or droplet-id> --tag-name mytag
returns the error message:
Error: POST https://api.digitalocean.com/v2/tags/testing/resources: 404 The resource you were accessing could not be found.
The text was updated successfully, but these errors were encountered: