Jeremy, I missed this whole discussion. I really noticed by checking the latest commit. I'm sorry if I miss anything prior to that.
I saw in the blueprint this parameter as an example: | Name |Config File | Value | Profile | |--------------------------------------------------|--------------------------|--------------------------------------|-----------| | location | url_sig_myds.config | /opt/trafficserver/etc/trafficserver | EDGE | In the past, these DS specific parameters have been causing trouble (cloning an older profile with a DS that doesn't exist anymore, but location still does). Is there anything in this blueprint that helps with that? Steve On Mon, Dec 13, 2021 at 11:44 AM Jeremy Mitchell <[email protected]> wrote: > Hi everyone. If you have feedback for Rima on her blueprint, may I ask that > you get it in this week so we can move forward with the development of this > feature: https://github.com/apache/trafficcontrol/pull/6095 > > 4 months is probably ample time :) > > thanks! > > On Tue, Aug 10, 2021 at 12:46 PM Shah, Rima <[email protected] > > > wrote: > > > Hello All, > > > > > > I’ve opened a PR to propose a new feature for Traffic Control: Layered > > Profiles. Layered Profiles allow assigning multiple profiles, in order, > to > > both Servers and Delivery Services. Layered Profiles is exactly as > powerful > > as the existing profiles, it doesn't enable any new things. It makes > > profiles much easier to manage. > > > > Please take a look at it and let me know your thoughts. > > > > The blueprint can be found at: > > https://github.com/apache/trafficcontrol/pull/6095 > > > > > > Thanks and Regard, > > Rima Shah > > > > >
