Conversation
|
Refer to this link for build results (access rights to CI server needed): |
432a02c to
8c609e6
Compare
|
Refer to this link for build results (access rights to CI server needed): |
8c609e6 to
4feaeaf
Compare
|
Refer to this link for build results (access rights to CI server needed): |
4feaeaf to
a9060f1
Compare
|
Refer to this link for build results (access rights to CI server needed): |
a9060f1 to
2ead12a
Compare
366cb53 to
516293c
Compare
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
516293c to
cf35a4c
Compare
|
Refer to this link for build results (access rights to CI server needed): |
cf35a4c to
cc778a2
Compare
|
Refer to this link for build results (access rights to CI server needed): |
2aa3fe0 to
0b72e5f
Compare
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
c007818 to
21fd6a9
Compare
Adds error logging whenever the config gen inserts multiple cacheurl or cachekey plugins on the same line. This isn't supported in ATS, and will usually do the wrong thing. But, we've always generated config like this, so for now, this doesn't change the config gen, but it logs the error
19b8d39 to
406f040
Compare
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
406f040 to
d099a22
Compare
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
ocket8888
left a comment
There was a problem hiding this comment.
I feel like there could be a lot more GoDoc comments in here, but then we don't have a style guide that enforces it (yet).
171aeee to
e71ec72
Compare
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
What does this PR (Pull Request) do?
Based on #3762 - highly recommend merging that first.
Converts remap.config to Traffic Ops Golang.
As with the other ATS configs, the code isn't ideal in some places, because it transliterates the Perl as closely as possible, for safety. I'm hoping we can convert these endpoints in two phases, transliterating, then refactoring, to be as safe as possible.
I've parity tested, against the old Perl for every production edge and mid we have, and they all diff identical (after sorting).
No documentation change, doesn't change the interface.
Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Request the remap.config endpoint for a server, request it from an older TO, make sure they're identical after sorting (for ATS, map lines can be in any order, and on each line, plugin directives can be in any order as long as the associated pparam directives following them are the same).
If this is a bug fix, what versions of Traffic Ops are affected?
Not a bug fix.
The following criteria are ALL met by this PR