3 ms·
i am not sure i would personally use this library/approach when scripting, a few reasons: Using a third-party libraries as core part of your infrastructure (ci
by hankchinaski 5y ago
i am not sure i would personally use this library/approach when scripting, a few reasons:
Using a third-party libraries as core part of your infrastructure (ci/cd scripts, provisioning, automation) implies a greater risk to potential security issues, "framework tax" ie. having to comply, learn, document, debug its custom APIs, having to deal with potential limitations, issues that either needs to be fixed upstream or result in the library being forked and therefore maintained in house. I would rather either put together a set of bash commands or - if the problem entails a more comprehensive endeavour with greater complexity - put together a in-house tool/library where i can make the right compromises from day one