-
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
Support labels for google cloud resources #3546
Comments
Judging from the info in the article it's a replacement for tags, but tags that previously existed are shown as value-less keys, which first led me to believe it used the tags system, but it's separately set with
|
I've tested using metadata for it, but it's not what they use below the covers and doesn't unlock the new features. I can wait for the feature to go out of beta though. |
I'm asking the SetLabel team internally to see if they have an estimate for when it will leave beta. |
|
Hey! Any update on this? It would be a brilliant way for us to track costs across different deployments... |
Regarding to official documentation of Google Cloud Platform labels are no more in beta |
Hi @lwander , can you remove the upstream label please ? Labels update on resource need to provide right fingerprint. It would be great to have common functions, that we could use in resource and datasource files. Thanks ! |
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. |
According to http://googlecloudplatform.blogspot.nl/2015/10/using-labels-to-organize-Google-Cloud-Platform-resources.html you can now use key/value pairs to label your resources.
It seem to be tags that have key=value format, but if I try that I get the following error, so apparently it's handled differently through the gcloud api.
Please add support for this as it will allow us to use this to label our resources for better cost reporting.
The text was updated successfully, but these errors were encountered: