rawlinp commented on a change in pull request #4819: URL: https://github.com/apache/trafficcontrol/pull/4819#discussion_r444440124
########## File path: blueprints/tags.md ########## @@ -0,0 +1,421 @@ +<!-- +Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. +--> +# Tags + +## Problem Description +Tags are a fairly long-requested feature; to be able to associate a key word or +phrase with a Delivery Service, or a user. Today, some organizations are abusing +the overloaded "description" properties of a Delivery Service to provide +comma-separated key words and phrases, essentially inventing their own tags by Review comment: Key-value tags would allow operators to essentially create whatever informational fields that they may want on a delivery service that might not make sense for everyone else's installation. For instance, maybe Company A wants to create "service categories" for delivery services in order to group them and do certain things with those groups outside the scope of TO. Company B might not care about or even want service categories, so instead of it just always being an empty, unused field in Company B's delivery services, it could exist purely in Company A's world via key-value tags. ---------------------------------------------------------------- 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: [email protected]
