When starting with cdist, the documentation and examples can be
overwheliming. Further more, sometimes one would only want to do a
simple test to see if the basics are working. One such example currently
is to create a simple remote file. While this is a nice and simple
example, an even simpler example would be to just see if we can 'ping'
the host.
Other configuration management tools also seem to have this as a basic
starting command.
This thus allows to do:
echo __ping | cdist config --initial-manifest - <host>
as the most basic, most simple command to 'test' things with, without
having lingering files to boot.
Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>
The command `echo -- -g` prints `-- -g` so the generated `groupadd` command
was syntactically incorrect and failing. Solution was to remove `--` since
echo command does not understand it, and add instead an extra space before
`-g` to avoid echo interpreting it as a flag.
* [type/__timezone] Whitelist OpenBSD
OpenBSD ships /etc/localtime and /usr/share/zoneinfo by default.
* [type/__postgres_{database,role}] Add explorer support for OpenBSD
On OpenBSD the "postgres" user is called "_postgresql".
The "postgres" database must me specifically specified as it differs from the
user name.
* [type/__postgres_{database,role}] Add gencode support for OpenBSD
On OpenBSD the "postgres" user is called "_postgresql".
The "postgres" database must me specifically specified when using psql as it
differs from the user name.
* [type/__postgres_role] Query DB if role exists instead of screen scaping
* [type/__postgres_database] Query DB if database exists instead
* [type/__postgres_{database,role}] Add user for NetBSD
* [type/__postgres_extension] Add support for OpenBSD and NetBSD
* [__ssh_authorized_key] Add OpenBSD support to entry explorer
Make sure to adhere to re_format(7) for OpenBSD compatibility.
https://man.openbsd.org/re_format.7
* [type/__start_on_boot] Add support for OpenBSD
sideeffect42