Add PuppetCore gem source support to module_ci workflow #129
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gavindidrichsen
force-pushed
the
puppetcore
branch
from
58e65f7 to
d15a267
Compare
- Add ruby_version input parameter with default of '2.7' - Add puppetcore_api_type input parameter with default of 'forge-key' - Configure environment variables for Puppet Core authentication - Update ruby-version in workflow to use the input parameter - Add documentation on requirements for enabling PuppetCore Signed-off-by: Gavin Didrichsen <[email protected]>
gavindidrichsen
force-pushed
the
puppetcore
branch
from
3d669d0 to
2c51e06
Compare
gavindidrichsen
changed the title
Verification using a puppetcore repositoryThis provision PR introduces puppetcore and re-uses the new shared
The main advantage of this change to the Verification using a non-puppetcore repositoryFurther, this 
|
Signed-off-by: Gavin Didrichsen <[email protected]>
Signed-off-by: Gavin Didrichsen <[email protected]>
gavindidrichsen
added a commit
to puppetlabs/provision
that referenced
this pull request
Mar 31, 2025
One of the cat-github-actions re-usable workflows has been updated to switch on the puppetcore. For reference see <puppetlabs/cat-github-actions#129>. This means a minor admustment is required on any modules that also need to run against puppetcore. One, `ruby_version` must be passed in and be >= 3.1; and two, the `PUPPET_FORGE_TOKEN` must be a secret on the repository. Signed-off-by: Gavin Didrichsen <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR enhances the module_ci reusable workflow to support the PuppetCore private gem source. This allows modules using this workflow to access private Puppet gems when needed.
Changes
PUPPET_FORGE_TOKEN. This "secret" is then in turn used to set theBUNDLE_RUBYGEMS___PUPPETCORE__PUPPET__COMwhich enables authenticated access to the puppetcore gemsALSO added a how to document for consumers of this re-usable module, see
docs/how-to/how_to_using_module_ci_workflow_with_puppetcore_gems.mdImpact
module_ci.ymlhas been verified with both a puppetcore enabled module https://github.com/puppetlabs/provision and a non-puppetcore one https://github.com/puppetlabs/puppetlabs-apache. See in the comments below for proof of testing.