Change Details

As part of Q1 OKRs, we want to spin off from Spicerack some of its modules and functionalities that can be useful to any other script/framework/tool. The idea is to have a standalone library that can be included anywhere, potentially even installing it in our base system directly. It should be available both as a Debian package and a PyPI module. It should not required specific configuration files for the library, just the ones eventually needed by the specific modules, eventually with a sane default for the path to the configuration file (TBD where to put them). The final list of functionalities/modules that should be spin off is TBD, this below is an initial draft: [ ] actions [ ] administrative [ ] config [ ] decorators? (TBD, has some Spicerack-specific logic about dry-run detection) [ ] dns [ ] interactive (part of it) [ ] the SAL logging part of the log module [ ] phabricator [ ] prometheus? (TBD)

As part of Q1 OKRs, we want to spin off from Spicerack some of its modules and functionalities that can be useful to any other script/framework/tool. The idea is to have a standalone library that can be included anywhere, potentially even installing it in our base system directly. It should be available both as a Debian package and a PyPI module. It should not required specific configuration files for the library, just the ones eventually needed by the specific modules, eventually with a sane default for the path to the configuration file (TBD where to put them). The final list of functionalities/modules that should be spin off is TBD, this below is an initial draft: [ ] actions [ ] administrative [ ] config [ ] decorators? (TBD, has some Spicerack-specific logic about dry-run detection) [x] dns [ ] interactive (part of it) [ ] the SAL logging part of the log module [ ] phabricator [ ] prometheus? (TBD)

As part of Q1 OKRs, we want to spin off from Spicerack some of its modules and functionalities that can be useful to any other script/framework/tool. The idea is to have a standalone library that can be included anywhere, potentially even installing it in our base system directly. It should be available both as a Debian package and a PyPI module. It should not required specific configuration files for the library, just the ones eventually needed by the specific modules, eventually with a sane default for the path to the configuration file (TBD where to put them). The final list of functionalities/modules that should be spin off is TBD, this below is an initial draft: [ ] actions [ ] administrative [ ] config [ ] decorators? (TBD, has some Spicerack-specific logic about dry-run detection) [ x] dns [ ] interactive (part of it) [ ] the SAL logging part of the log module [ ] phabricator [ ] prometheus? (TBD)