yage
8427ad40f0
===================================================================== Reminder of the deprecation notices for FZF_(HEAD|TAIL) and v3 runstrings! These will be removed in 4.2 (the next minor release!) --- Changes ------------------------------ - removed executable "run" in favor of single "scwrypts" entrypoint (this used to make more sense when running from the executable in the repository directly, but now scwrypts is primarily interfaced through the application itself) - EKS commands will now attempt cluster login if the kubectl context is not detected on your machine - improved warning messages for when scwrypts is out-of-date in API / CI contexts --- Bug Fixes ---------------------------- - zsh/utils/io print functions will now always print if no SCWRYPTS_LOG_LEVEL is defined |
||
|---|---|---|
| .. | ||
| cloud | ||
| db/postgres | ||
| docker | ||
| helm | ||
| lib | ||
| media/youtube | ||
| misc | ||
| office | ||
| redis | ||
| scwrypts | ||
| system | ||
| hello-world | ||
| README.md | ||
| sanity-check | ||
ZSH Scwrypts
Since they emulate direct user interaction, shell scripts are often the straightforward choice for task automation.
Basic Utilities
One of my biggest pet-peeves with scripting is when every line of a (insert-language-here) program is escaped to shell. This kind of program, which doesn't use language features, should be a shell script. While there are definitely unavoidable limitations to shell scripting, we can minimize a variety of problems with a modern shell and shared utilities library.
Loaded by common.zsh, the utils/ library provides:
- common function wrappers to unify flags and context
- lazy dependency and environment variable validation
- consistent (and pretty) user input / output