ocket8888 commented on a change in pull request #4819: URL: https://github.com/apache/trafficcontrol/pull/4819#discussion_r444423781
########## 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: I've relaxed the naming constraints to allow `_` and `=`, but I wouldn't recommend actually using tags for key/value pairs. If there's a key that's needed on Delivery Services, I'd rather see it as a proper property of DSes. Otherwise implementing that would essentially mean creating a model of Delivery Service that is mutable at runtime, which seems like a bad idea. ---------------------------------------------------------------- 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]
