ianc769 commented on issue #11608: URL: https://github.com/apache/cloudstack/issues/11608#issuecomment-3486621711
> [@ianc769](https://github.com/ianc769) , I saw [@shwstppr](https://github.com/shwstppr) ’s implementation and it looks good, but I do not see it as useful. usually tags are used for matching (hosts to compute offerings, templates to storage, etc) These tags do nothing as of yet. These are also not added to usage data, so for billing you would need outside scripting. Are you sure about the use-case/scenario and how it is helped by the PR [#11964](https://github.com/apache/cloudstack/pull/11964) ? Originally I was thinking something along the lines that AWS has: https://www.hashicorp.com/en/blog/default-tags-in-the-terraform-aws-provider ```hcl provider "aws" { default_tags { tags = { Environment = "Test" Owner = "TFProviders" Project = "Test" } } } ``` For our use case this is for cost allocation; If I have `product-alpha.my.domain.local` as a domain, I can look up metadata about it like - cost code - owner - email Now instead of tagging every object in the domain, I can just look at the domain itself (and all its resources with other API calls) to find out who owes me money 😂 Annotations would work, but I think this is much cleaner overall. Thoughts? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
