-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 #17
Comments
This comment was originally opened by @JorritSalverda as hashicorp/terraform#3546 (comment). It was migrated here as part of the provider split. The original comment is below. 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
|
This comment was originally opened by @lwander as hashicorp/terraform#3546 (comment). It was migrated here as part of the provider split. The original comment is below. Unfortunately this seems to only be available in the beta API. I'll have to see what might break if we move from v1 to beta. Have you considered using the |
This comment was originally opened by @JorritSalverda as hashicorp/terraform#3546 (comment). It was migrated here as part of the provider split. The original comment is below. 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. |
This comment was originally opened by @lwander as hashicorp/terraform#3546 (comment). It was migrated here as part of the provider split. The original comment is below. I'm asking the SetLabel team internally to see if they have an estimate for when it will leave beta. |
This comment was originally opened by @devth as hashicorp/terraform#3546 (comment). It was migrated here as part of the provider split. The original comment is below.
|
This comment was originally opened by @dvianello as hashicorp/terraform#3546 (comment). It was migrated here as part of the provider split. The original comment is below. Hey! Any update on this? It would be a brilliant way for us to track costs across different deployments... |
This comment was originally opened by @zbikmarc as hashicorp/terraform#3546 (comment). It was migrated here as part of the provider split. The original comment is below. Regarding to official documentation of Google Cloud Platform labels are no more in beta |
This comment was originally opened by @tpoindessous as hashicorp/terraform#3546 (comment). It was migrated here as part of the provider split. The original comment is below. 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 ! |
It's now available since #142 But it would be nice to have common functions. Thanks |
Hey @tpoindessous, I'm not sure what you mean by common functions, but @selmanj is working on adding support for labels, generally. |
Hi I was thinking about helpers functions, which everyone can use instead of rewriting code for using labels. For example, I'm trying to add a new datasource for snapshot and I added support for searching by labels in my fork
It would be useful to reduce code by using helpers functions. Thanks for your work and your future work ;) Thomas |
@tpoindessous I, too, don't like repeating myself. I'll use a helper function for sure here to reduce duplication. Thanks for the suggestion! |
It's awesome that there is labels support for compute_instances! But are there any plans of extending labels support to other resources in near future? |
There is a Work In Progress to add it for snapshot resource :)
Le ven. 7 juil. 2017 à 10:53, Marcin Żbik <[email protected]> a
écrit :
… It's awesome that there is labels support for compute_instances! But are
there any plans of extending labels support to other resources in near
future?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC6cEKZzzjhU0g42Eq3-xxrSHQNIMnIVks5sLfHpgaJpZM4N4fuk>
.
|
Added label support to |
Any plans to add it to |
@zbikmarc Yes, it's planned. I'll prioritize that resource when I get a chance. |
Opened #515 |
Closing for now. Labels have been added to:
Feel free to file subsequent issues if you find any other resources that need labels. |
Is it possible to add label support for
|
Hi, I filed a separate issue (#1372) to track this. Thanks for reporting. |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
This issue was originally opened by @JorritSalverda as hashicorp/terraform#3546. It was migrated here as part of the provider split. The original body of the issue is below.
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: