confdroid/confdroid_automatic
1
0
Fork 0
Code Issues Projects Wiki Activity

Compare commits

base: confdroid:master
Branches Tags
confdroid:master
confdroid:1.0.0
..
compare: confdroid:b775086a6208b5b125c61195a22abcbd54c223ec
Branches Tags
confdroid:master
confdroid:1.0.0

1 Commits
master ... b775086a62

Author SHA1 Message Date
Jenkins
b775086a62 Merge branch 'jenkins-build-5' into 'master' 
Auto-merge for build 5

See merge request puppet/confdroid_automatic!4
 2026-03-30 13:50:56 +02:00
3 changed files with 71 additions and 91 deletions
Expand all files Collapse all files

42
README.md
View File

@@ -2,7 +2,7 @@
[![Build Status](https://jenkins.confdroid.com/buildStatus/icon?job=confdroid_automatic&style=plastic)](https://jenkins.confdroid.com/job/confdroid_automatic/)
[![Security Hotspots](https://sonarqube.confdroid.com/api/project_badges/measure?project=confdroid_automatic&metric=security_hotspots&token=sqb_c40a62afc3787918ade945dbc43089bb68ea7ab1)](https://sonarqube.confdroid.com/dashboard?id=confdroid_automatic)
[![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/grizzlycoda/puppet_collection)
- [Readme](#readme)
- [Synopsis](#synopsis)
- [WARNING](#warning)
@@ -10,19 +10,16 @@
- [Dependencies](#dependencies)
- [Support](#support)
- [Parameter Inheritance](#parameter-inheritance)
- [SELINUX](#selinux)
- [Deployment](#deployment)
- [Module Deployment](#module-deployment)
- [Tests](#tests)
- [Contact Us](#contact-us)
- [Disclaimer](#disclaimer)
## Synopsis
dnf-automatic is a mechanism to allow automatic OS updates for Rocky 9 and similar RHEL 9 based operating systems.
dnf-automatic is a mechanism to allow automatic OS updates for Rocky 9.
`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.
`confdroid_automatic` manages dnf-automatic installations and configurations.
## WARNING
@@ -30,8 +27,8 @@ Choose the required update and reboot policy per host, host group, environment e
## Features
- install required binaries,
- manage files and directories with proper selinux context
- install required binaries, files and services
- manage selinux context
- manage main configurations files via parameters
- manage service
@@ -39,34 +36,16 @@ Choose the required update and reboot policy per host, host group, environment e
## Support
- Rocky 9 (any RHEL 9-based OS should work)
- Rocky 9
- 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
## Module Deployment
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
```ruby
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.
See [more details about class deployment on confdroid.com](https://confdroid.com/2017/05/deploying-our-puppet-modules/).
ALmost every puppet setup is done in very custom ways, and hence the way the modules are deployed to nodes are different. This module assumes [Foreman][def] as ENC, so the modules just have to be present on the master node and Foreman will take care for it.
## Tests
@@ -76,7 +55,6 @@ See [more details about class deployment on confdroid.com](https://confdroid.com
- Puppet Parser
- ERB Template Parser
- Sonar Quality Gate
- End-to-end deployments in Rocky-9 environments
## Contact Us
@@ -87,3 +65,5 @@ See [more details about class deployment on confdroid.com](https://confdroid.com
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.
[def]: https://www.theforeman.org/manuals/3.13/quickstart_guide.html

60
doc/file.README.html
View File

@@ -60,16 +60,37 @@
<div id="content"><div id='filecontents'>
<h1 id="label-Readme">Readme</h1>
<p><a href="https://jenkins.confdroid.com/job/confdroid_automatic/"><img src="https://jenkins.confdroid.com/buildStatus/icon?job=confdroid_automatic&amp;style=plastic"></a> <a href="https://sonarqube.confdroid.com/dashboard?id=confdroid_automatic"><img src="https://sonarqube.confdroid.com/api/project_badges/measure?project=confdroid_automatic&amp;metric=security_hotspots&amp;token=sqb_c40a62afc3787918ade945dbc43089bb68ea7ab1"></a> <a href="https://deepwiki.com/grizzlycoda/puppet_collection"><img src="https://deepwiki.com/badge.svg"></a> - <a href="#readme">Readme</a> - <a href="#synopsis">Synopsis</a> - <a href="#warning">WARNING</a> - <a href="#features">Features</a> - <a href="#dependencies">Dependencies</a> - <a href="#support">Support</a> - <a href="#parameter-inheritance">Parameter Inheritance</a> - <a href="#selinux">SELINUX</a> - <a href="#deployment">Deployment</a> - <a href="#tests">Tests</a> - <a href="#contact-us">Contact Us</a> - <a href="#disclaimer">Disclaimer</a></p>
<p><a href="https://jenkins.confdroid.com/job/confdroid_automatic/"><img src="https://jenkins.confdroid.com/buildStatus/icon?job=confdroid_automatic&amp;style=plastic"></a> <a href="https://sonarqube.confdroid.com/dashboard?id=confdroid_automatic"><img src="https://sonarqube.confdroid.com/api/project_badges/measure?project=confdroid_automatic&amp;metric=security_hotspots&amp;token=sqb_c40a62afc3787918ade945dbc43089bb68ea7ab1"></a></p>
<ul><li>
<p><a href="#readme">Readme</a></p>
</li><li>
<p><a href="#synopsis">Synopsis</a></p>
</li><li>
<p><a href="#warning">WARNING</a></p>
</li><li>
<p><a href="#features">Features</a></p>
</li><li>
<p><a href="#dependencies">Dependencies</a></p>
</li><li>
<p><a href="#support">Support</a></p>
</li><li>
<p><a href="#parameter-inheritance">Parameter Inheritance</a></p>
</li><li>
<p><a href="#module-deployment">Module Deployment</a></p>
</li><li>
<p><a href="#tests">Tests</a></p>
</li><li>
<p><a href="#contact-us">Contact Us</a></p>
</li><li>
<p><a href="#disclaimer">Disclaimer</a></p>
</li></ul>
<h2 id="label-Synopsis">Synopsis</h2>
<p>dnf-automatic is a mechanism to allow automatic OS updates for Rocky 9 and similar RHEL 9 based operating systems.</p>
<p>dnf-automatic is a mechanism to allow automatic OS updates for Rocky 9.</p>
<p><code>confdroid_automatic</code> manages dnf-automatic installations and configurations.</p>
<p>Choose the required update and reboot policy per host, host group, environment etc. Set the email notification about updates, that’s all it needs.</p>
<h2 id="label-WARNING">WARNING</h2>
<blockquote>
@@ -78,9 +99,9 @@
<h2 id="label-Features">Features</h2>
<ul><li>
<p>install required binaries,</p>
<p>install required binaries, files and services</p>
</li><li>
<p>manage files and directories with proper selinux context</p>
<p>manage selinux context</p>
</li><li>
<p>manage main configurations files via parameters</p>
</li><li>
@@ -91,7 +112,7 @@
<h2 id="label-Support">Support</h2>
<ul><li>
<p>Rocky 9 (any RHEL 9-based OS should work)</p>
<p>Rocky 9</p>
</li><li>
<p>Puppet 8</p>
</li></ul>
@@ -100,28 +121,9 @@
<p>All parameters are listed in <code>params.pp</code> 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.</p>
<h2 id="label-SELINUX">SELINUX</h2>
<h2 id="label-Module+Deployment">Module Deployment</h2>
<p>All files and directories are configured with correct selinux context. If selinux is disabled, these contexts are ignored.</p>
<h2 id="label-Deployment">Deployment</h2>
<ul><li>
<p>native Puppet deployment</p>
</li></ul>
<p>via site.pp or nodes.pp</p>
<pre class="code ruby"><code class="ruby">node &#39;example.example.net&#39; {
include confdroid_automatic
}
</code></pre>
<ul><li>
<p>through Foreman:</p>
</li></ul>
<p>In order to apply parameters through Foreman, <strong>confdroid_automatic::params</strong>- must be added to the host or host group in question.</p>
<p>See <a href="https://confdroid.com/2017/05/deploying-our-puppet-modules/">more details about class deployment on confdroid.com</a>.</p>
<p>ALmost every puppet setup is done in very custom ways, and hence the way the modules are deployed to nodes are different. This module assumes <a href="https://www.theforeman.org/manuals/3.13/quickstart_guide.html">Foreman</a> as ENC, so the modules just have to be present on the master node and Foreman will take care for it.</p>
<h2 id="label-Tests">Tests</h2>
<ul><li>
@@ -137,8 +139,6 @@
<p>ERB Template Parser</p>
</li><li>
<p>Sonar Quality Gate</p>
</li><li>
<p>End-to-end deployments in Rocky-9 environments</p>
</li></ul>
<h2 id="label-Contact+Us">Contact Us</h2>

60
doc/index.html
View File

@@ -60,16 +60,37 @@
<div id="content"><div id='filecontents'>
<h1 id="label-Readme">Readme</h1>
<p><a href="https://jenkins.confdroid.com/job/confdroid_automatic/"><img src="https://jenkins.confdroid.com/buildStatus/icon?job=confdroid_automatic&amp;style=plastic"></a> <a href="https://sonarqube.confdroid.com/dashboard?id=confdroid_automatic"><img src="https://sonarqube.confdroid.com/api/project_badges/measure?project=confdroid_automatic&amp;metric=security_hotspots&amp;token=sqb_c40a62afc3787918ade945dbc43089bb68ea7ab1"></a> <a href="https://deepwiki.com/grizzlycoda/puppet_collection"><img src="https://deepwiki.com/badge.svg"></a> - <a href="#readme">Readme</a> - <a href="#synopsis">Synopsis</a> - <a href="#warning">WARNING</a> - <a href="#features">Features</a> - <a href="#dependencies">Dependencies</a> - <a href="#support">Support</a> - <a href="#parameter-inheritance">Parameter Inheritance</a> - <a href="#selinux">SELINUX</a> - <a href="#deployment">Deployment</a> - <a href="#tests">Tests</a> - <a href="#contact-us">Contact Us</a> - <a href="#disclaimer">Disclaimer</a></p>
<p><a href="https://jenkins.confdroid.com/job/confdroid_automatic/"><img src="https://jenkins.confdroid.com/buildStatus/icon?job=confdroid_automatic&amp;style=plastic"></a> <a href="https://sonarqube.confdroid.com/dashboard?id=confdroid_automatic"><img src="https://sonarqube.confdroid.com/api/project_badges/measure?project=confdroid_automatic&amp;metric=security_hotspots&amp;token=sqb_c40a62afc3787918ade945dbc43089bb68ea7ab1"></a></p>
<ul><li>
<p><a href="#readme">Readme</a></p>
</li><li>
<p><a href="#synopsis">Synopsis</a></p>
</li><li>
<p><a href="#warning">WARNING</a></p>
</li><li>
<p><a href="#features">Features</a></p>
</li><li>
<p><a href="#dependencies">Dependencies</a></p>
</li><li>
<p><a href="#support">Support</a></p>
</li><li>
<p><a href="#parameter-inheritance">Parameter Inheritance</a></p>
</li><li>
<p><a href="#module-deployment">Module Deployment</a></p>
</li><li>
<p><a href="#tests">Tests</a></p>
</li><li>
<p><a href="#contact-us">Contact Us</a></p>
</li><li>
<p><a href="#disclaimer">Disclaimer</a></p>
</li></ul>
<h2 id="label-Synopsis">Synopsis</h2>
<p>dnf-automatic is a mechanism to allow automatic OS updates for Rocky 9 and similar RHEL 9 based operating systems.</p>
<p>dnf-automatic is a mechanism to allow automatic OS updates for Rocky 9.</p>
<p><code>confdroid_automatic</code> manages dnf-automatic installations and configurations.</p>
<p>Choose the required update and reboot policy per host, host group, environment etc. Set the email notification about updates, that’s all it needs.</p>
<h2 id="label-WARNING">WARNING</h2>
<blockquote>
@@ -78,9 +99,9 @@
<h2 id="label-Features">Features</h2>
<ul><li>
<p>install required binaries,</p>
<p>install required binaries, files and services</p>
</li><li>
<p>manage files and directories with proper selinux context</p>
<p>manage selinux context</p>
</li><li>
<p>manage main configurations files via parameters</p>
</li><li>
@@ -91,7 +112,7 @@
<h2 id="label-Support">Support</h2>
<ul><li>
<p>Rocky 9 (any RHEL 9-based OS should work)</p>
<p>Rocky 9</p>
</li><li>
<p>Puppet 8</p>
</li></ul>
@@ -100,28 +121,9 @@
<p>All parameters are listed in <code>params.pp</code> 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.</p>
<h2 id="label-SELINUX">SELINUX</h2>
<h2 id="label-Module+Deployment">Module Deployment</h2>
<p>All files and directories are configured with correct selinux context. If selinux is disabled, these contexts are ignored.</p>
<h2 id="label-Deployment">Deployment</h2>
<ul><li>
<p>native Puppet deployment</p>
</li></ul>
<p>via site.pp or nodes.pp</p>
<pre class="code ruby"><code class="ruby">node &#39;example.example.net&#39; {
include confdroid_automatic
}
</code></pre>
<ul><li>
<p>through Foreman:</p>
</li></ul>
<p>In order to apply parameters through Foreman, <strong>confdroid_automatic::params</strong>- must be added to the host or host group in question.</p>
<p>See <a href="https://confdroid.com/2017/05/deploying-our-puppet-modules/">more details about class deployment on confdroid.com</a>.</p>
<p>ALmost every puppet setup is done in very custom ways, and hence the way the modules are deployed to nodes are different. This module assumes <a href="https://www.theforeman.org/manuals/3.13/quickstart_guide.html">Foreman</a> as ENC, so the modules just have to be present on the master node and Foreman will take care for it.</p>
<h2 id="label-Tests">Tests</h2>
<ul><li>
@@ -137,8 +139,6 @@
<p>ERB Template Parser</p>
</li><li>
<p>Sonar Quality Gate</p>
</li><li>
<p>End-to-end deployments in Rocky-9 environments</p>
</li></ul>
<h2 id="label-Contact+Us">Contact Us</h2>