GitHub puppet-catalog-diff
📄↔📄 A tool to diff Puppet catalogs

Repo Checks ( 16 of 26 successfull )
Metadata Valid
No translation
passed
Correct Puppet Version Range
Supported Puppet version range is %{PUPPET_SUPPORT_RANGE}
failed
With Puppet Version Range
Puppet version range is present in requirements in metadata.json
passed
With Operatingsystem Support
No translation
passed
Operatingsystems
No translation
passed
Supports Only Current Centos
No translation
passed
Supports Latest Centos
No translation
failed
Supports Only Current Oraclelinux
No translation
passed
Supports Latest Oraclelinux
No translation
failed
Supports Only Current Redhat
No translation
passed
Supports Latest Redhat
No translation
passed
Supports Only Current Scientific
No translation
passed
Supports Latest Scientific
No translation
failed
Supports Only Current Debian
No translation
failed
Supports Latest Debian
No translation
failed
Supports Only Current Ubuntu
No translation
passed
Supports Latest Ubuntu
No translation
failed
Supports Only Current Windows
No translation
passed
Supports Latest Windows
No translation
failed
In Modulesync Repo
Is listed as a module managed using modulesync_config
passed
Synced
Has a .msync.yml file
passed
Latest Modulesync
Has been synchronized with the latest tagged version of modulesync_config
passed
Has Modulesync
Is present in voxpupuli/modulesync_config/managed_modules.yml
passed
Released
Is in modulesync_config and in forge releases.
failed
Valid Sync File
If a (optional) sync file is present, it must not contain a `.travis.yml` entry.
passed
Reference Dot Md
The repository has a REFERENCE.md. It needs to be generated / puppet-strings documentation is missing.
failed

Open Pull Requests

Improve viewer class (fully qualify ht_crypt)

Pull Request (PR) description

The viewer class was failing to compile when used on puppet 7. This is because the ht_crypt function usage needed to be fully qualified.

Open PR in GitHub
modulesync 5.4.0
modulesync

modulesync 5.4.0

Open PR in GitHub
Fix failed nodes report

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

Fix visibility on failed nodes in the output report for the Catalog Diff Viewer

PR 50 introduced a bug where the pulloutput is not being added to the nodes hash when the report is written.
Adding pull
output back to the nodes hash to be written to the json report.
This allows the Catalog Diff Viewer to see failed nodes in the report.

Changing the compile catalog to print body instead of reason when a compile fails as it provides the log entry with reason why compile failed for the node.

This Pull Request (PR) fixes the following issues

Fixes #92

Open PR in GitHub
modulesync 7.5.0
modulesync

modulesync 7.5.0

Open PR in GitHub
Allow trusted facts to be derived from node name

Allow trusted facts to be derived from node name

When using the certless API, Puppet will use trusted facts from PuppetDB unless provided in the request. If the PuppetDB facts were uploaded by the catalogdiff host, the trusted facts in PuppetDB will be for the catalogdiff host rather than the node being evaluated. This allows the trusted facts to be derived from the node name instead of using values from PuppetDB.

Perhaps there is a way to have Puppet store the trusted facts as presented in the facts file being uploaded, but from what I can tell the facts API always replaces trusted facts with data derived from the client cert.

Open PR in GitHub