Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Manage modules manifests using ModuleSync #3

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Conversation

smortex
Copy link
Collaborator

@smortex smortex commented Sep 3, 2024

All puppet modules managed with this repo are supposed to share a similar manifests/init.pp file, but in reality these files have slight differences that ModuleSync allows to avoid.

Also, the modules on the Puppet forge have quite a bad quality score partly due to some style issues (example), so this PR also improve this.

This code will be needed in another file.  Modulesync does not seem to
have built-in support for adding utility methods, so just put them in
a local file and require it where the methods are needed.
This file is supposed to provide access to the same parameters for all
choria modules, but some modules are lacking one or more of these
parameters.  By managing its content with modulesync, we ensure we have
consistent interface for all modules.
These checks are performed on the Puppet Forge to give quality scores to
modules, and are failing for the choria repositories:
* The `ensure` parameter must be the first one in resource declaration;
* Non-interpolated strings should be single, not double-quoted.

A bunch of other issues are reported by puppet-lint, but as of today
they do not seem to be part of the module score calculation, so in order
to minimize changes, this commit do not address them.

While these changes are gratuitous, they will allow the scoring of the
modules to increase, giving users a more positive view of the care taken
to maintain them.
@smortex smortex marked this pull request as ready for review September 3, 2024 17:31
@ripienaar
Copy link
Contributor

hmm, missed this one, its good to go @smortex ?

@smortex
Copy link
Collaborator Author

smortex commented Sep 19, 2024

hmm, missed this one, its good to go @smortex ?

It is good to go.

You can review the changes that it wants to makes in the modules by looking at the "noop run / Run msync --noop against all modules (pull_request)" test above, and expand the "Run msync --noop" section.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants