Rocky Linux uses yum repos to define its download sources.
+
+
resources_cd is a Puppet module to automate installation and
+configuration of common yum repos.
+
+
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
+
+
installs and configures yum repos
+
+
+
Repo Documentation
+
+
See the full Puppet documentation including parameters in
+docs/index.html
+
+
Dependencies
+
+
All dependencies must be included in the catalogue.
+
+
Deployment
+
+
native Puppet deployment
+
+
+
via site.pp or nodes.pp
+
+
node 'example.example.net' {
+ include cd_kubernetes
+}
+
+
+
through Foreman:
+
+
+
In order to apply parameters through Foreman, the params.pp must be added
+to the host or host group in question.
All files and directories are configured with correct selinux context. If
+selinux is disabled, these contexts are ignored.
+
+
Known Problems
+
+
Support
+
+
OS: Rocky 9
+
+
Puppet 6,8
+
+
+
Tests
+
+
Puppet Lint
+
+
excluded tests:
+
+
--no-class_inherits_from_params_class-check:relevant only to
+non-supported outdated puppet versions
+
+
--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.
+
+
--no-80chars-check: it is not always possible to stay within
+80 characters, although typically only occurring on the parameter vault
+params.pp.
+
+
--no-arrow_alignment-check: this check leads to actually not
+having am easily readable arrow alignment, as this checks per
+block, not per class.
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..1310783
--- /dev/null
+++ b/doc/frames.html
@@ -0,0 +1,17 @@
+
+
+
+
+ Documentation by YARD 0.9.26
+
+
+
+
diff --git a/doc/index.html b/doc/index.html
new file mode 100644
index 0000000..5e6c1f9
--- /dev/null
+++ b/doc/index.html
@@ -0,0 +1,184 @@
+
+
+
+
+
+
+ File: README
+
+ — Documentation by YARD 0.9.26
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Rocky Linux uses yum repos to define its download sources.
+
+
resources_cd is a Puppet module to automate installation and
+configuration of common yum repos.
+
+
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
+
+
installs and configures yum repos
+
+
+
Repo Documentation
+
+
See the full Puppet documentation including parameters in
+docs/index.html
+
+
Dependencies
+
+
All dependencies must be included in the catalogue.
+
+
Deployment
+
+
native Puppet deployment
+
+
+
via site.pp or nodes.pp
+
+
node 'example.example.net' {
+ include cd_kubernetes
+}
+
+
+
through Foreman:
+
+
+
In order to apply parameters through Foreman, the params.pp must be added
+to the host or host group in question.
All files and directories are configured with correct selinux context. If
+selinux is disabled, these contexts are ignored.
+
+
Known Problems
+
+
Support
+
+
OS: Rocky 9
+
+
Puppet 6,8
+
+
+
Tests
+
+
Puppet Lint
+
+
excluded tests:
+
+
--no-class_inherits_from_params_class-check:relevant only to
+non-supported outdated puppet versions
+
+
--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.
+
+
--no-80chars-check: it is not always possible to stay within
+80 characters, although typically only occurring on the parameter vault
+params.pp.
+
+
--no-arrow_alignment-check: this check leads to actually not
+having am easily readable arrow alignment, as this checks per
+block, not per class.
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.