-
Notifications
You must be signed in to change notification settings - Fork 351
Renamed rascal to tm/traffic_monitor #7068
Conversation
ocket8888
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As Rawlin said, we can't just change what TO is querying for when it looks for Parameters or servers etc. That would break a lot of things on install, that would take a while to fix by hand through the API. In a database migration, though, it should be pretty simple to swap out the old names for the new ones.
Yeah, I have a commit to push the new migration files. |
0dfe20f to
882263a
Compare
traffic_ops/app/db/migrations/2022100610190300_update_rascal_to_traffic_monitor.up.sql
Outdated
Show resolved
Hide resolved
882263a to
d94dbd2
Compare
ocket8888
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the following references to RASCAL can be removed from the documentation
./docs/source/overview/profiles_and_parameters.rst: .. warning:: For legacy reasons, the names of Profiles of this type *must* begin with ``RASCAL_``. This is **not** enforced by the :ref:`to-api` or Traffic Portal, but certain Traffic Control operations/components expect this and will fail to work otherwise!
./docs/source/admin/traffic_monitor.rst: .. note:: For legacy compatibility reasons, the 'Type' field of a new Traffic Monitor server must be 'RASCAL'.
Closes: #2564 from RASCAL (Traffic Monitor) Perspective
Which Traffic Control components are affected by this PR?
t3c, formerly ORT)What is the best way to verify this PR?
If this is a bugfix, which Traffic Control versions contained the bug?
PR submission checklist