feat: minimal mlab-ns compatibility shim#252
Conversation
f37707b to
c4fca10
Compare
|
I am now looking into the failures. Let's first deal with the linting failures: I agree with the second and the third. The first one, TBH, is a matter of code style and I am not super happy about this level of exaggerated linting for arguably more correct code ( With respect to the tests proper, the failure is this: and it happens while uploading to coveralls. So, this also needs to be investigated. |
6fc738e to
f0b4771
Compare
Fixed the second and the third one. Disable |
This is a coveralls outage and there's not much that we can do but wait 🙄 |
|
@robertodauria coveralls is up and running again! Please, take a look! 🙏 |
88b456d to
f0b4771
Compare
We implement a minimal mlab-ns compatibility shim. The service has been EOL for a long time now. We recently reached out to integrators and it seems there are still some that need a small compatibility shim to avoid breaking legacy applications. Their migration is fully underway, but there needs to be time to migrate a fleet of legacy clients, which are using the output of mlab-ns for archival purposes. Accordingly, this pull request implements just the minimum functionality to avoid breaking those applications. Yet, note that the returned response is not actionable anymore for running ndt5 tests (and it can't be used for running ndt7 tests either). The complete plan is this: 1. merge this diff 2. deploy 3. use `dispatch.yaml` to route to `locate` 4. discontinue `mlab-ns` 5. wait for the legacy applications queue to drain 6. circle back and zap this diff This is probably the last chapter in mlab-ns glorious life. See #185. Adapted from #184.
f0b4771 to
ba23c75
Compare
Pull Request Test Coverage Report for Build 22629741708Details
💛 - Coveralls |
We implement a minimal mlab-ns compatibility shim.
The service has been EOL for a long time now. We recently reached out to integrators and it seems there are still some that need a small compatibility shim to avoid breaking legacy applications.
Their migration is fully underway, but there needs to be time to migrate a fleet of legacy clients, which are using the output of mlab-ns for archival purposes.
Accordingly, this pull request implements just the minimum functionality to avoid breaking those applications. Yet, note that the returned response is not actionable anymore for running ndt5 tests (and it can't be used for running ndt7 tests either).
The complete plan is this:
merge this diff
deploy
use
dispatch.yamlto route tolocatediscontinue
mlab-nswait for the legacy applications queue to drain
circle back and zap this diff
This is probably the last chapter in mlab-ns glorious life.
See #185.
Adapted from #184.
This change is