Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Change remaining `maid` references

See original GitHub issue

I gather that the project, initially called janitor, has gone through a couple name changes (though I don’t find issues or PRs discussing either):

to maid in a9c508d974b356993eb70e9cb33c86276cecb719, and
to custodian in 6e92a203d59524b3c3060b951e5cd109e6a94ca4.

I don’t find any more references to janitor (only to Netflix’s Janitor Monkey, by way of comparison). I do find a few remaining references to maid, however, and I’m interested in extirpating those, to alleviate future users and developers of unnecessary cognitive overhead (“Wait … what the heck is Maid?”). I’ve picked off the least controversial in https://github.com/capitalone/cloud-custodian/pull/778. The rest appear to be more difficult to change, because they are in tag names that we depend on (e.g., maid_offhours) or even a message format specifier. More research required!

Issue Analytics

State:
Created 7 years ago
Comments:13 (10 by maintainers)

Top GitHub Comments

1reaction

kapiltcommented, Dec 29, 2016

Yeah those name changes where pre-open sourcing of the code base and we had many extant internal users so places where there would have been impacted by the name change in the code, where left as is. Historical raisons

0reactions

kapiltcommented, Jun 28, 2019

yeah that would be useful, its actually possible to customize the target namespace now as well on cli