Version information
This version is compatible with:
- Puppet Enterprise 2023.8.x, 2023.7.x, 2023.6.x, 2023.5.x, 2023.4.x, 2023.3.x, 2023.2.x, 2023.1.x, 2023.0.x, 2021.7.x, 2021.6.x, 2021.5.x, 2021.4.x, 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x
- Puppet >= 7.0.0 < 9.0.0
- , , , , , ,
Start using this module
Add this module to your Puppetfile:
mod 'puppet-hdm', '3.3.0'
Learn more about managing modules with a PuppetfileDocumentation
puppet-hdm
Table of Contents
Description
This module manages the betadots HDM installation.
HDM can be installed on Puppet Server or on any other system with PuppetDB access and Puppet code deployed.
This module allows you to either make use of the betadots HDM Docker container or to install HDM using RVM.
Major Update
As of version 1.0.0 and newer the HDM Docker container runs in production mode. Existing installations using HDM container prior version 1.0.0 must prepare this change by copying the development.sqlite3 file to production.sqlite3
cp /etc/hdm/development.sqlite3 /etc/hdm/production.sqlite3
Now Puppet can configure the system. Once HDM is up and running the database can be changed from development to production:
docker exec -ti hdm /hdm/bin/rails db:environment:set RAILS_ENV=production
After the update and checking functionality the development.sqlite3 file can be deleted.
Setup
Setup Requirements
The puppet-hdm module needs puppetlabs/stdlib as we use some of the stdlib data types.
If you want to make use of the docker container, you need the following module:
- puppetlabs/docker - min version 4.4.0
If you want to install HDM using RVM, you need the following modules:
- puppet/rvm - min version 2.0.0
- golja/gnupg - min version 1.2.3
- puppetlabs/vcsrepo - min version 5.2.0
- puppet/systemd - min version 3.10.0
SLES and Docker module
The puppetlabs-docker Module lacks official SLES and SuSe support. Yet: the module is usable on SLES.
The installation of Docker can not be done using the module on SLES. Instead one must install Docker separately within a profile class.
But any other defined type like docker::image
or docker::run
is working.
One must set the acknowledge_unsupported_os
parameter to true
to prevent the Docker module from failing on SuSe systems.
Hiera:
---
# Allow Docker to work on SLES
docker::acknowledge_unsupported_os: true
Beginning with betadots HDM
The most simple approach is to just include the hdm class and provide the version parameter:
include hdm
You can find the released versions on HDM releases page
hdm::version: '1.0.1
Another option is to use class resource type declaration:
class { 'hdm':
version => '1.0.1',
}
This will install HDM as docker container.
Reference
Please check the REFERENCE.md file.
Limitations
On SLES we can not use the puppetlabs/docker module. Instead set the manage_docker parameter to false and take care on docker package and service by yourself.
Transfer Notice
This Puppet module was originally authored by betadots GmbH. The maintainer preferred that Vox Pupuli take ownership of the module for future improvement and maintenance. Existing pull requests and issues were transferred over, please fork and continue to contribute here instead of github.com/betadots/puppet-hdm.
License
This module is licensed under the Apache-2 license.
Reference
Table of Contents
Classes
Public Classes
hdm
: HDM installation main class
Private Classes
hdm::docker
: Manage HDM using Dockerhdm::rvm
: Manage HDM using RVM
Data types
Hdm::Gitdata
: type to enforce git settings for HDMHdm::Ldap_settings
: type to enforce ldap settings for HDMHdm::Puppetdb
: type to enforce puppetdb settings for HDM
Classes
hdm
This class controls the installation of HDM
Examples
include hdm
Parameters
The following parameters are available in the hdm
class:
method
manage_docker
version
container_registry_url
ruby_version
port
bind_ip
hostname
timezone
hdm_path
secret_key_base
git_url
user
group
puppetdb_settings
puppet_dir
puppet_code_dir
disable_authentication
allow_encryption
read_only
git_data
ldap_settings
ldap_bind_dn_password
hdm_hiera_config_file
custom_lookup_function
method
Data type: Enum['docker', 'rvm']
Select the installation method. Available methods: docker, rvm When using rvm we install rvm into system and add the bundler gem.
Default value: 'docker'
manage_docker
Data type: Boolean
Set to false if this module should NOT also include the docker class (without any arguments) Please note that the docker module only works on Debian, RedHat and windows systems. SLES users must install and start docker via puppet package and service resource.
Default value: true
version
Data type: String[1]
Select the version to deploy. Version is the image tag name when using docker and the git tag when using rvm Please find the releases on HDM website: https://github.com/betadots/hdm/releases
Default value: '3.0.0'
container_registry_url
Data type: String[1]
Configure another registry. Contains the host, path and container name. The version is set via the version parameter. e.g. ghcr.io/betadots/hdm
Default value: 'ghcr.io/betadots/hdm'
ruby_version
Data type: String[1]
Select the ruby version when installing using rvm Please check hdm ruby version requirement
Default value: '3.3.1'
port
Data type: Stdlib::Port
The port where HDM should run on
Default value: 3000
bind_ip
Data type: Stdlib::IP::Address::Nosubnet
The ip address to bind the process to
Default value: '0.0.0.0'
hostname
Data type: String[1]
The HDM webservice hostname
Default value: $facts['networking']['fqdn']
timezone
Data type: String[1]
THe timezone to use when running with docker
Default value: $facts['timezone']
hdm_path
Data type: Stdlib::Unixpath
Path where one wants to install and configure hdm
Default value: '/etc/hdm'
secret_key_base
Data type: String[1]
A secret key. Key can be generated using openssl rand -hex 16
Default value: '7a8509ab31fdb0c15c71c941d089474a'
git_url
Data type: String[1]
The git URL to clone the hdm repo from
Default value: 'https://github.com/betadots/hdm.git'
user
Data type: String[1]
The hdm user name
Default value: 'hdm'
group
Data type: String[1]
The hdm group name
Default value: 'hdm'
puppetdb_settings
Data type: Hdm::Puppetdb
A hash to provide information on how HDM can connect to puppetdb The following options are possible: Plain text (default)
{
'server' => 'http://localhost:8080',
}
Using PE token:
{
'server' => 'https://localhost:8081',
'token' => '/etc/hdm/puppetdb.token',
'cacert' => '<path to cacert>',
}
Using SSL cert:
{
'server' => 'https://localhost:8081',
'pem' => {
'key' => '/etc/hdm/ssl.key',
'cert' => '/etc/hdm/ssl.cert',
'ca_file' => '/etc/hdm/ssl.ca',
},
}
Default value: { 'server' => 'http://localhost:8080', }
puppet_dir
Data type: Stdlib::Unixpath
The path where HDM can find the global hiera.yaml file defaults to '/etc/puppetlabs'
Default value: '/etc/puppetlabs'
puppet_code_dir
Data type: Stdlib::Unixpath
The path where HDM can find deployed Puppet environments (similar to puppet config code_dir) defaults to '/etc/puppetlabs/code'
Default value: '/etc/puppetlabs/code'
disable_authentication
Data type: Boolean
Disable user and login This makes HDM available to anyone.
Default value: false
allow_encryption
Data type: Boolean
Specify if HDM should use EYAML Needs HDM access to EYAML keys (public and private) Values for keys are taken from hiera.yaml file and can not be set individually.
Default value: false
read_only
Data type: Boolean
Set to false if you want the ability to change data via HDM webfrontend. WARNING!! setting to true is untested!!! Changes are stored via GIT. Setting this to true also needs the git_data Array parameter
Default value: true
git_data
Data type: Optional[Hdm::Gitdata]
Configure several settings related to the option to modify data via Webfrontend. WARNING!! untested!! Required Array of hash data:
[
{
'datadir' => 'modules/hieradata/data',
'git_url' => 'git@server:path/repo.git',
'path_in_repo' => 'data',
'ssh_priv_key' => '.ssh/id_rsa',
}
]
Default value: undef
ldap_settings
Data type: Optional[Hdm::Ldap_settings]
Config for LDAP integration Needs the following Hash:
{
'host' => 'localhost',
'port' => 389,
'base_dn' => 'ou=hdm,dc=nodomain',
'bind_dn' => 'cn=admin,dc=nodomain',
'bind_dn_password' => 'openldap', # clear text
'ldaps' => false,
}
Default value: undef
ldap_bind_dn_password
Data type: Optional[Sensitive[String[1]]]
set sensitive password for ldap bind
Default value: undef
hdm_hiera_config_file
Data type: String[1]
Set to another file if you want HDM to not use hiera.yaml.
Default value: 'hiera.yaml'
custom_lookup_function
Data type: Hash[String[1],Enum['yaml', 'eyaml']]
If you use your own developed hiera lookup function, HDM needs to know if the function returns yaml or eyaml data. Example:
{
'functon_name' => '<yaml|eyaml>'
}
Default value: `{}`
## Data types
### <a name="Hdm--Gitdata"></a>`Hdm::Gitdata`
type to enforce git settings for HDM
Alias of
```puppet
Array[Struct[
{
datadir => Stdlib::Unixpath,
git_url => String[1],
path_in_repo => String[1],
Optional[ssh_priv_key] => String[1],
}
]]
Hdm::Ldap_settings
type to enforce ldap settings for HDM
Alias of
Struct[{
'host' => Stdlib::Host,
'port' => Stdlib::Port,
'base_dn' => String[1],
'bind_dn' => String[1],
'bind_dn_password' => Optional[Variant[Sensitive[String[1]],String[1]]],
'ldaps' => Boolean,
}]
Hdm::Puppetdb
type to enforce puppetdb settings for HDM
Alias of
Struct[{
server => Stdlib::Httpurl,
Optional[pem] => Struct[
{
key => Stdlib::Unixpath,
cert => Stdlib::Unixpath,
ca_file => Stdlib::Unixpath,
}
],
Optional[token] => Stdlib::Unixpath,
Optional[cacert] => Stdlib::Unixpath,
}]
Changelog
All notable changes to this project will be documented in this file. Each new release typically also includes the latest modulesync defaults. These should not affect the functionality of the module.
v3.3.0 (2024-11-21)
Implemented enhancements:
- Updates on config and spec #98 (tuxmea)
- Update ruby version and hdm version defaults #89 (rwaffen)
- Add Puppet 8 support #87 (zilchms)
- puppetlabs/docker: Allow 9.x #86 (zilchms)
- puppetlabs/vcsrepo: Allow 6.x #85 (zilchms)
- puppet/systemd: Allow 6.x #84 (zilchms)
- puppet/rvm: Allow 3.x #83 (zilchms)
- puppetlabs/stdlib: allow 9.x #82 (zilchms)
Merged pull requests:
v3.2.0 (2024-03-14)
Implemented enhancements:
- Manage option to use a custom lookup function #80 (tuxmea)
- HDM supports disabling authentication. #77 (tuxmea)
v3.1.0 (2024-01-11)
Implemented enhancements:
Closed issues:
- SLES Support missing in docker implementation #68
Merged pull requests:
v3.0.0 (2023-06-19)
Breaking changes:
- Drop Puppet 6 support #56 (bastelfreak)
Implemented enhancements:
- Allow setting of different hiera.yaml to use #60 (tuxmea)
- Switch version from main to fix version. #54 (tuxmea)
v2.2.1 (2023-02-17)
Merged pull requests:
- README.md: Fix license badge #49 (bastelfreak)
v2.2.0 (2023-02-17)
Implemented enhancements:
- puppet-lint: validate docs and datatypes #48 (bastelfreak)
Merged pull requests:
- Update documentation: make more clear where the product originates from #47 (rwaffen)
- .fixtures.yml: Migrate from forge releases to git #45 (bastelfreak)
- Migrate module from betadots to Vox Pupuli #44 (bastelfreak)
- puppet/systemd: Allow 4.x #43 (bastelfreak)
v2.1.2 (2023-02-16)
Implemented enhancements:
- Update Gems + CI config #39 (bastelfreak)
Fixed bugs:
Closed issues:
- Adapt changes from HDM #30
Merged pull requests:
- Fix syntax highlighting in README.md #37 (bastelfreak)
v2.1.1 (2023-01-31)
Merged pull requests:
- minor update and new release #36 (tuxmea)
- fixes for production #35 (tuxmea)
- Release v2.0.0 #34 (tuxmea)
v2.0.2 (2023-01-30)
v2.0.1 (2023-01-30)
v2.0.0 (2023-01-30)
Closed issues:
- mark passwords as sensitive #22
Merged pull requests:
- preparation for v1 container running in production mode #33 (tuxmea)
- Add badges to README.md #32 (bastelfreak)
- update docker and apt module versions #31 (tuxmea)
- restart if config file changes #29 (tuxmea)
- improve data types #28 (tuxmea)
- Manage changelog #27 (tuxmea)
- prepare v1.2.3 #26 (tuxmea)
- Create LICENSE #14 (tuxmea)
- Update issue templates #13 (tuxmea)
- Create CODE_OF_CONDUCT.md #12 (tuxmea)
v1.2.3 (2022-12-09)
Closed issues:
- ldaps config not working #23
v1.2.2 (2022-12-09)
Implemented enhancements:
- Add assert_private() to private classes #17 (bastelfreak)
Fixed bugs:
- Debian Docker: Configure correct shell for hdm user #20 (bastelfreak)
Merged pull requests:
v1.2.1 (2022-08-10)
Merged pull requests:
v1.2.0 (2022-08-08)
Merged pull requests:
- update new release to v1.2.0 #11 (tuxmea)
- installation via RVM #10 (tuxmea)
- new release v1.1.1 #9 (tuxmea)
v1.1.0 (2022-08-04)
Merged pull requests:
v1.0.3 (2022-08-04)
Merged pull requests:
v1.0.2 (2022-08-04)
v1.0.1 (2022-08-04)
Merged pull requests:
v1.0.0 (2022-08-03)
Merged pull requests:
- Use hdm data types on complex hashes and arrays #3 (tuxmea)
- Add GitHub actions #2 (tuxmea)
- Docker #1 (tuxmea)
* This Changelog was automatically generated by github_changelog_generator
Dependencies
- puppetlabs/stdlib (>= 4.13.0 < 10.0.0)
- puppetlabs/docker (>= 4.4.0 < 11.0.0)
- puppetlabs/vcsrepo (>= 5.2.0 < 7.0.0)
- golja/gnupg (>= 1.2.3 < 2.0.0)
- puppet/rvm (>= 2.0.0 < 4.0.0)
- puppetlabs/apt (>= 8.5.0 < 10.0.0)
- puppet/systemd (>= 3.10.0 < 8.0.0)
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.