dnf-automatic is a mechanism to allow automatic OS updates for Rocky 9 and similar RHEL 9 based operating systems.
+
+
confdroid_automatic manages dnf-automatic installations and configurations.
+
+
Choose the required update and reboot policy per host, host group, environment etc. Set the email notification about updates, that’s all it needs.
+
+
WARNING
+
+
+
Attention: Never use this puppet module on systems which have been previously configured manually. It is impossible to predict how and what would have been configured, hence previous configurations outside the scope of this module may be overwritten! Automated configurations require a test environment to verify that the module suits the purpose intended by the user, as well as tune the parameters, before deploying into live production
+
+
+
Features
+
+
install required binaries,
+
+
manage files and directories with proper selinux context
+
+
manage main configurations files via parameters
+
+
manage service
+
+
+
Dependencies
+
+
Support
+
+
Rocky 9 (any RHEL 9-based OS should work)
+
+
Puppet 8
+
+
+
Parameter Inheritance
+
+
All parameters are listed in params.pp and inherited from there. Variable parameters are in the upper section and also documented in the top. These can be overridden by the ENC. Parameters in the bottom section (curly brackets) cannot be overridden and usually are used for keeping the code in the classes more readable.
+
+
SELINUX
+
+
All files and directories are configured with correct selinux context. If selinux is disabled, these contexts are ignored.
+
+
Deployment
+
+
native Puppet deployment
+
+
+
via site.pp or nodes.pp
+
+
node 'example.example.net' {
+ include confdroid_automatic
+}
+
+
+
through Foreman:
+
+
+
In order to apply parameters through Foreman, confdroid_automatic::params- must be added to the host or host group in question.
--no-variable_scope-check: not applicable as we are inheriting parameters from params class. the lint check does not distinguish between facts and inherited parameters.
ConfDroid as entity is entirely independent from Puppet. We provide custom configuration modules, written for specific purposes and specific environments. The modules are tested and supported only as documented, and require testing in designated environments (i.e. lab or development environments) for parameter tuning etc. before deploying into production environments.
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/doc/frames.html b/doc/frames.html
new file mode 100644
index 0000000..53734c2
--- /dev/null
+++ b/doc/frames.html
@@ -0,0 +1,22 @@
+
+
+
+
+ Documentation by YARD 0.9.36
+
+
+
+
diff --git a/doc/index.html b/doc/index.html
new file mode 100644
index 0000000..1712b7c
--- /dev/null
+++ b/doc/index.html
@@ -0,0 +1,187 @@
+
+
+
+
+
+
+ File: README
+
+ — Documentation by YARD 0.9.36
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
dnf-automatic is a mechanism to allow automatic OS updates for Rocky 9 and similar RHEL 9 based operating systems.
+
+
confdroid_automatic manages dnf-automatic installations and configurations.
+
+
Choose the required update and reboot policy per host, host group, environment etc. Set the email notification about updates, that’s all it needs.
+
+
WARNING
+
+
+
Attention: Never use this puppet module on systems which have been previously configured manually. It is impossible to predict how and what would have been configured, hence previous configurations outside the scope of this module may be overwritten! Automated configurations require a test environment to verify that the module suits the purpose intended by the user, as well as tune the parameters, before deploying into live production
+
+
+
Features
+
+
install required binaries,
+
+
manage files and directories with proper selinux context
+
+
manage main configurations files via parameters
+
+
manage service
+
+
+
Dependencies
+
+
Support
+
+
Rocky 9 (any RHEL 9-based OS should work)
+
+
Puppet 8
+
+
+
Parameter Inheritance
+
+
All parameters are listed in params.pp and inherited from there. Variable parameters are in the upper section and also documented in the top. These can be overridden by the ENC. Parameters in the bottom section (curly brackets) cannot be overridden and usually are used for keeping the code in the classes more readable.
+
+
SELINUX
+
+
All files and directories are configured with correct selinux context. If selinux is disabled, these contexts are ignored.
+
+
Deployment
+
+
native Puppet deployment
+
+
+
via site.pp or nodes.pp
+
+
node 'example.example.net' {
+ include confdroid_automatic
+}
+
+
+
through Foreman:
+
+
+
In order to apply parameters through Foreman, confdroid_automatic::params- must be added to the host or host group in question.
--no-variable_scope-check: not applicable as we are inheriting parameters from params class. the lint check does not distinguish between facts and inherited parameters.
ConfDroid as entity is entirely independent from Puppet. We provide custom configuration modules, written for specific purposes and specific environments. The modules are tested and supported only as documented, and require testing in designated environments (i.e. lab or development environments) for parameter tuning etc. before deploying into production environments.