ocket8888 commented on issue #7027:
URL:
https://github.com/apache/trafficcontrol/issues/7027#issuecomment-1219680361
I really think we ought not to let people modify "Parameters" as a
first-class object. It's confusing at best. Like if you have a Profile A with
some Parameter in CDN 1, then make Profile B in CDN 2 and use a POST request to
[`/profiles/{{ID}}/parameters`](https://traffic-control-cdn.readthedocs.io/en/latest/api/v4/profiles_id_parameters.html)
to add a Parameter to Profile B, then if it just so happens to have the same
name, "ConfigFile", and value as some Parameter on A, you have silently created
"linked" Profiles such that modifying the Parameter of one you actually now
change two Profiles - escaping the CDN assignment boundary between them as
well. TP will warn you of this, but automation gets nothing.
Even through Traffic Portal that has problems, because once you get into
that situation the only way around it is to delete the Parameter from one
Profile and then create a new Parameter with the value you want it to have and
then assign it back to the Profile again. A three step process to change as
little as one character.
For my money, Parameters ought to be nothing more than a collection property
of Profiles. Especially now that we have the ability to clone and export/import
Profiles to reduce the effort to reproduce common configurations, and Profile
layering to reduce duplication of configuration.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
