Extending the "Tag" feature to function more like AWS Tags which are key/value metadata elements.

Extending the "Tag" feature to function more like AWS Tags which are key/value metadata elements.

0 vote

avatar

I like the idea of being able to associate "Tags" with various records within my RDP deployment. The one thing I wish it supported was the ability to create them as a "key / value" pair. This has been very useful in my AWS environments since I'm able to define a tag like:

Tag Key | Tag Value
Environment Stage (or Dev | Test | Prod, etc)
Instance Type Physical | Virtual
HyperVisor Hyper-V | vSphere | XCP-NG

This helps when performing script automations because I can easily filter my targets to those with the Environment tag set to Stage or a set of values. Helps with reporting breakdown, etc.

I'm sure this would be impactful when deployments have existing "non-keyed" tags created for the various records configured within their RDM deployment.

Just wanted to throw this out there for consideration.

All Comments (2)

avatar

Hello,

Thank you for your suggestion. As it stands, in RDM, a lot of these can be set in the entry, but it doesn't seem to be as flexible as what you are suggesting.

For example, the environment can be set in the asset version.



The virtual environment type can be set in the network tab.



You can also set server role types.



If those fields are acceptable for you, we would only need to add the possibility to search for those here.



Let me know if this would work for you, have a good day!

Maxime Morin

image (35).png

image (34).png

image (32).png

image (31).png

avatar

Thank you for the detailed response and guidance! I will give this a shot and see how far I can get with these.

My thought was to be able to apply a "filter query" on the Navigational tree on the left. Something that I found helpful in applications like Jira or XCP-NG.

  • Select a Default Filter Queries: This would filter my tree view to only those assets / entries that matched the name/value tags (The Field/Asset fields would work just fine).
  • Drop down to switch to other predefined Filter Queries; i.e.: Lab Infrastructure + Shared Services; Weekly Maintenance Assets; Performance Testing; Team A; Team B; etc.


Thanks again and I'll give your suggestions a shot.
George