========
Changes
-------
- Rename commands to plugins in pelconf
As we’re changing a lot in pelconf right now in anticipation of v1.0 release,
one of those things is the name of commands/plugins. Since commands is not
really a thing anymore as most of that can be handled by scripts, it makes
more sense to name this section ‘plugins’ instead.
- All project configuration now lives in cfg: section
The config values are no longer loaded from the file top-level values.
Instead, `pelconf.yaml` should define a `cfg:` section at top level and
expose those values to peltak and scripts.
- Remove the old way of defining scripts
You cannot define scripts inside pelconf.yaml anymore, you just put the .sh
files into your `scripts_dir` and add a header comment to denote they should
be loaded by peltak. This is much more conveniant for the user and makes the
config and scripts much more readable.
- Rename peltak.commands to peltak.cli
Shorter and fits more into the new architecture. This will break a lot of
things, so it’s probably one of the last moments to od this, since the whole
architecture is changing right now. Move to scripts as being the core
functionality already changes a lot and will probably be the final shape for
v1.0. The old way of defining scripts will be dropped soon as well.