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, 2021.7.x
- Puppet >= 7.24 < 9.0.0
- , , , , , , , , ,
Tasks:
- run_cd4pe_job
Start using this module
Add this module to your Puppetfile:
mod 'puppetlabs-cd4pe_jobs', '1.7.0'Learn more about managing modules with a PuppetfileDocumentation
cd4pe_jobs
This module exists for Continuous Delivery for Puppet Enterprise to run jobs on Puppet Agents via Bolt. It contains a single task to do this and works with both *nix and Windows.
To run tests (from root of repo):
bundle exec rspec spec
Release puppetlabs-cd4pe_jobs
- Create a branch off
masterusing the following convention:
git checkout -b 1.6.0-release
- On a new branch based on the release branch, update CHANGELOG.md with any changes in this release and metadata.json with the new version number.
- Commit these changes and put up a PR against the release branch you created in Step 1 and get review.
- Once the changes have been approved and merged to the release branch, pull down the updated release branch and tag the module.
git tag -a 1.6.0 -m "1.6.0"
- Run
pdk build --forcein the root of the module to get the new tarball. Theforceflag is required because this module is not fully compatible with modern PDK versions, and we don't want the PDK to attempt to convert anything. This is the same thing we do with thecd4peadmmodule. - Log into https://forge.puppet.com as 'puppetlabs' and publish the new module version
- Update the ref in PE: https://github.com/puppetlabs/pe-tasks-vanagon/blob/main/configs/components/puppetlabs-cd4pe_jobs.json. This will ensure that the new version is shipped with the next PE release.
- Push your new tag up to the repo
git push --tags
- Make a PR from the release branch back to
master. Once this is merged the release branch should be deleted.
What are tasks?
Modules can contain tasks that take action outside of a desired state managed by Puppet. It’s perfect for troubleshooting or deploying one-off changes, distributing scripts to run across your infrastructure, or automating changes that need to happen in a particular order as part of an application deployment.
Tasks in this module release
Change Log
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
[Unreleased]
No unreleased changes.
1.7.0
Added
- Added podman support for containerized jobs. If podman is detected on a job hardware node, it will be used instead of docker.
1.6.3
Fixed
- Fixed misleading Puppet version requirements accidentally released in 1.6.2.
1.6.2
Fixed
- Fixed issue in tarball unpacking where pax header lines were causing some long filenames to be truncated.
1.6.1
Fixed
- Updated module to use File#exist? instead of deprecated (and removed in Ruby 3.2.0/Puppet 8) File#exists?
1.6.0
Added
- Added optional parameter for passing in secrets that should be set as environment variables before running the job script
1.5.0
Added
- Added verbose logging for failed http requests.
1.4.0
Added
- Added the ability to include registry credentials when pulling the Docker image.
- Added the ability to trust registries that use the same CA as CD4PE when pulling the Docker image.
1.3.0
Added
- Added the ability to pass a custom net http timeout to jobs in order to increase the time a job waits for a response when hitting CD4PE endpoints.
1.2.1
Fixed
- Fixed a problem where jobs with large output could hang indefinitely.
1.2.0
Fixed
- Improved support for jobs with substantial log output.
1.1.1
Fixed
- No longer fail when setting \$HOME on windows machines.
1.1.0
Added
- When writing job scripts, user now has access to HOME and REPO_DIR environment variables.
Fixed
- Increase read_timeout to 600 to accomadate large repositories
1.0.0
Initial release: Support for running jobs for Continuous Delivery for Puppet Enterprise on Puppet Agents managed by the Puppet Enterprise Orchestrator.
Quality checks
We run a couple of automated scans to help you assess a module’s quality. Each module is given a score based on how well the author has formatted their code and documentation and select modules are also checked for malware using VirusTotal.
Please note, the information below is for guidance only and neither of these methods should be considered an endorsement by Puppet.
Malware scan results
The malware detection service on Puppet Forge is an automated process that identifies known malware in module releases before they’re published. It is not intended to replace your own virus scanning solution.
Learn more about malware scans- Module name:
- puppetlabs-cd4pe_jobs
- Module version:
- 1.7.0
- Scan initiated:
- July 25th 2024, 14:36:29
- Detections:
- 0 / 65
- Scan stats:
- 65 undetected
- 0 harmless
- 0 failures
- 0 timeouts
- 0 malicious
- 0 suspicious
- 14 unsupported
- Scan report:
- View the detailed scan report