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

Compare commits

base: confdroid:febf9f494d4bc5cd03f7da0d3e49b03eba46d6db
Branches Tags
confdroid:master
confdroid:1.0.1-04.2026 confdroid:1.0.0-04.2026
..
compare: confdroid:14c19ec01027d3e3233290a1aa907968ed0b2eb6
Branches Tags
confdroid:master
confdroid:1.0.1-04.2026 confdroid:1.0.0-04.2026

5 Commits
febf9f494d ... 14c19ec010

Author SHA1 Message Date
Jenkins
14c19ec010 Merge branch 'jenkins-build-32' into 'master' 
Auto-merge for build 32

See merge request puppet/confdroid_ssh!32
 2026-04-14 13:09:44 +02:00
Jenkins Server
6578688e1f Recommit for updates in build 32 2026-04-14 13:00:52 +02:00
Jenkins Server
cb5b517900 Merge remote-tracking branch 'origin/master' into jenkins-build-32 2026-04-14 12:59:54 +02:00
12ww1160
12d58a30f7 OP#577 update Readme 2026-04-14 12:59:37 +02:00
Jenkins
7a0a60b12b Merge branch 'jenkins-build-31' into 'master' 
Auto-merge for build 31

See merge request puppet/confdroid_ssh!31
 2026-04-14 10:48:21 +00:00
3 changed files with 3 additions and 3 deletions
Expand all files Collapse all files

2
README.md
View File

@@ -43,7 +43,7 @@ All parameters are listed in `params.pp` and inherited from there. Variable par
## Module Deployment
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.
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

2
doc/file.README.html
View File

@@ -121,7 +121,7 @@
<h2 id="label-Module+Deployment">Module Deployment</h2>
<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>
<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>

2
doc/index.html
View File

@@ -121,7 +121,7 @@
<h2 id="label-Module+Deployment">Module Deployment</h2>
<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>
<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>