Skip to content
This repository was archived by the owner on Nov 24, 2025. It is now read-only.
This repository was archived by the owner on Nov 24, 2025. It is now read-only.

Legacy Naming Conventions (Rascal, RIAK, CCR et. al.) #2564

@ocket8888

Description

@ocket8888

It's super confusing that Traffic Monitor is referred to in hundreds of places as "Rascal", Traffic Vault as "RIAK" and Traffic Router as CCR. We should change those.

That would also entail removing legacy constraints related to those names, e.g. Traffic Monitor profiles currently must start with a "RASCAL" prefix for no good reason I've ever heard. Database tables and columns ought to be renamed as well (if applicable, I'm not sure), but that probably would make production upgrades much more complicated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Traffic Monitorrelated to Traffic MonitorTraffic Opsrelated to Traffic OpsTraffic Routerrelated to Traffic RouterTraffic Vaultrelated to Traffic Vaultlow difficultythe estimated level of effort to resolve this issue is lowlow impactaffects only a small portion of a CDN, and cannot itself break onenew featureA new feature, capability or behaviortech debtrework due to choosing easy/limited solution

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions