New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rewrote /dbdump to Go #3912
Rewrote /dbdump to Go #3912
Conversation
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): |
b4036c1
to
903d967
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): |
903d967
to
3cc10d5
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): |
261d309
to
9ce28e3
Compare
Refer to this link for build results (access rights to CI server needed): |
9ce28e3
to
1ed7e08
Compare
Refer to this link for build results (access rights to CI server needed): |
1ed7e08
to
6b1ab30
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): |
6b1ab30
to
72d151b
Compare
Refer to this link for build results (access rights to CI server needed): |
72d151b
to
8c6db93
Compare
Refer to this link for build results (access rights to CI server needed): |
8c6db93
to
fa25d2d
Compare
Refer to this link for build results (access rights to CI server needed): |
d9beb1e
to
f6d9b08
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): |
f6d9b08
to
65fae7d
Compare
Refer to this link for build results (access rights to CI server needed): |
infrastructure/cdn-in-a-box/traffic_ops_integration_test/run.sh
Outdated
Show resolved
Hide resolved
Also now cleaning up files after diff
65fae7d
to
c5d2295
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): |
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.
looks good
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.
works as expected
What does this PR (Pull Request) do?
Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Call the endpoint and use the response data as the input to
pg_restore
- verify the resulting database is identical to the one dumped at the time it was dumped. I don't know how that could be tested as a unit test, so I didn't write one. I also think it's generally inadvisable to use this endpoint, as a full dump of what is essentially an implementation detail of the API through the API itself seems like an un-document-able nightmare. I'd advise system engineers in need of recreating and/or backing up the database do so by directly using thepg_dump
tool, rather than the TO API.The following criteria are ALL met by this PR