[GitHub] [trafficcontrol] rawlinp commented on pull request #4819: Tags blueprint

[GitBox <gi...@apache.org>]

rawlinp commented on pull request #4819:
URL: https://github.com/apache/trafficcontrol/pull/4819#issuecomment-843368781


   Tags are meant to be purely informational only. If anything within TO actually acts upon or changes behavior based on tag data, that is a bug. Think "long_desc_1" and "long_desc_2" instead of profiles/parameters. The former is purely informational from ATC's perspective, whereas the latter actually affects system behavior.
   
   I think there is tremendous power in being able to provide arbitrary data on ATC resources (servers, DSes, phys_locations, etc) that ATC is not itself responsible for whatsoever (other than providing the ability to CRUD that arbitrary data). People can add whatever arbitrary data they want, ensure that they conform to whatever external schema's they want, and make external systems act on that data however they want. As long as it's purely informational from ATC's perspective, I don't really have an issue with tags. It's not really profiles/parameters++.


-- 
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org