README
¶
⚠ Importing this client via un-versioned
github.com/apache/trafficcontrol/traffic_ops/clientpaths is deprecated! Usegithub.com/apache/trafficcontrol/traffic_ops/v3-client(for API v3.0) instead.
Traffic Ops is the tool for administration (configuration and monitoring) of all components in a Traffic Control CDN. The CDN administrator uses Traffic Ops to manage servers, cache groups, delivery services, etc. In many cases, a configuration change requires propagation to several, or even all, caches and only explicitly after or before the same change propagates to Traffic Router. Traffic Ops takes care of this required consistency between the different components and their configuration. Traffic Ops exposes its data through a series of HTTP APIs and has a user interface that is interactive and viewable using a standard web browser.
For more info see the Traffic Control Website
Directories
¶
| Path | Synopsis |
|---|---|
|
app
|
|
|
install
|
|
| * | |
|
testing
|
|
|
api/config
Package config provides tools to load and validate configuration data for Traffic Ops API tests.
|
Package config provides tools to load and validate configuration data for Traffic Ops API tests. |
|
api/v1/config
Package config provides testing helpers for Traffic Ops API tests.
|
Package config provides testing helpers for Traffic Ops API tests. |
|
api
Package api provides general purpose tools for implementing the Traffic Ops API.
|
Package api provides general purpose tools for implementing the Traffic Ops API. |
|
federation_resolvers
Package federation_resolvers contains handler logic for the /federation_resolvers and /federation_resolvers/{{ID}} endpoints.
|
Package federation_resolvers contains handler logic for the /federation_resolvers and /federation_resolvers/{{ID}} endpoints. |
|
iso
Package iso provides support for generating ISO images.
|
Package iso provides support for generating ISO images. |
|
monitoring
Package monitoring contains handlers and supporting logic for the /cdns/{{CDN Name}}/configs/monitoring Traffic Ops API endpoint.
|
Package monitoring contains handlers and supporting logic for the /cdns/{{CDN Name}}/configs/monitoring Traffic Ops API endpoint. |
|
routing
Package routing defines the HTTP routes for Traffic Ops and provides tools to register those routes with appropriate middleware.
|
Package routing defines the HTTP routes for Traffic Ops and provides tools to register those routes with appropriate middleware. |
|
routing/middleware
Package middleware provides symbols for HTTP "middleware" which wraps handlers to perform common behaviors, such as authentication, headers, and compression.
|
Package middleware provides symbols for HTTP "middleware" which wraps handlers to perform common behaviors, such as authentication, headers, and compression. |
|
server
Package server provides tools for manipulating the server database table and corresponding http handlers.
|
Package server provides tools for manipulating the server database table and corresponding http handlers. |
|
swaggerdocs/v13
Package docs Traffic Ops API
|
Package docs Traffic Ops API |
|
Package client provides Go bindings to the Traffic Ops RPC API.
|
Package client provides Go bindings to the Traffic Ops RPC API. |
|
Package client provides Go bindings to the Traffic Ops RPC API.
|
Package client provides Go bindings to the Traffic Ops RPC API. |
|
Package client implements methods for interacting with the Traffic Ops API.
|
Package client implements methods for interacting with the Traffic Ops API. |