That's something I hadn't thought of. Adding tags when the usage job runs
sounds like a better approach. It will also limit the potential number of
places where changes need to be made. I'm planning to include tags as an
array in a field or possible comma separated values.
Thanks,
-Syed
On Tue,
Hi Syed,
I see the use case and yes this could work – couple of things:
- Any resource could have multiple tags – would they all be included as an
array in a single DB field, or would you want to just define one specific tag (
e.g. “owner” or “costcentre”) and include that single field?
- How
