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
For some reason, the echo|grep pattern was enclosed four times in a $()
operation. Nothing happened, since grep is always invoked with -q
(quiet, nothing printed to stdout).
In the original order, stderr was connected to the old stdout
(terminal). This was _probably_ not intended. The new order fixes this
by first connecting stdout to /dev/null and then attaching stderr to
that as well.
- Update installation method, following official installation
instructions.
- docker-engine was renamed to Docker CE around March 2017. Update
manpage to reflect that change.
- Remove flag `--experimental` since it is no longer necessary to install a
different binary to get experimental features. Experimental features are
included in the stable binary and can be enabled by a flag or in a
config file.
* add an type explorer to unify detecting of package type.
* update currage use the type explorer, so if os and passed in type
does not match, it behaves correctly.
This type tried to disable an unit after it has removed it, which
failed. Now the removal happens in gencode-remote, after the unit has
been stopped and disabled.
Clarify that this type only operates on units in /etc/systemd/system.
Also, when state=present, it is not always true that the type is
"installed, enabled and started"
