Give the ability to tag/label a project
I'm excited to announce that we recently released tags on database deployments.
Tags on projects is coming soon! If you want to be one of the firsts to test out tags on projects, let me know!
I'm not familiar with AWS, but on Azure, all components have the possibility to add tags
The visibility and management of tags/labels allows us to add information specific to our organization. We use this information for different use cases.
-> Categorize a data asset (Availability, Integrity, Confidentiality) Tag: DIC=444. This allows us to identify if the asset is configured correctly.
-> Owner of a data asset. TAG: Owner = Individual Insurance; Contact = John Smith
-> Last Compliance Auditor Check: TAG: Compliance=2022-02-22; Listener = William Smith; Status = Passed
-> Associated system name
-> Cost center TAG: BillTo=CCCC-111232
These are just a few examples that we do with the use of tags/labels. Having it at the API level is handy, but having it at the UI level would be EXTREMELY helpful.
You may be aware that we offer tags for clusters today, but manageable via the API only and no currently visible in our UI or billing experience. It's also worth sharing for future readers that Project names are editable at any time, and many customers have been able to use this to organize their environments.
However, we are definitely keen to do more here and augment this to Projects in future. Members of our team will likely reach out to discuss more specifically but I would be curious to hear your use case for these: would it largely be for doing billing rollups/chargebacks or for other purposes like knowing which Projects are associated with which environments and use cases?
Out of curiosity, could you share what pain point the ability to tag/label projects would solve?