3
0

update Readme and add yum repo

This commit is contained in:
Arne Teuke
2025-02-26 14:16:33 +01:00
parent dab22875c6
commit d682791676
3 changed files with 44 additions and 3 deletions

View File

@@ -6,8 +6,42 @@
## Synopsis
This Puppet module configures settings for puppet master and puppet agents.
This Puppet module configures settings for Puppet master and agents, PuppetDB and R10k, the full bundle.
The syntax etc is specifically for Puppet Core 8 and Rocky 9, although might work elsewhere as well.
## 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 repo rpm
## Support
* Rocky 9
* Puppet Core 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.
* Puppet Parser
* ERB Template Parser
* Test for unwanted UTF8 files in the Puppet code (see tests/UTF_Files)
* Markdown-lint
* Spellcheck
* Sonar Quality Gate
## Contact Us
[contact Us](https://confdroid.com/contact/)
## Disclaimer
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.