Project

puppet_fixtures

0.01
No release in over 3 years
puppet_fixturesvoxpupuli/puppet_fixturesHomepageDocumentationSource CodeBug Tracker
Originally part of puppetlabs_spec_helper, but with a significant refactoring to make it available standalone.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
 Popularity
Downloads
90,210
Stars
0
Forks
5
Watchers
1
 Releases
Current version
2.2.0
Total releases
9
First release
1980-01-02
Latest release
1980-01-02
 Issues
Open Issues
2
Closed Issues
2
Total Issues
4
Issue Closure Rate
50%
 Pull Requests
Open Pull Requests
0
Closed Pull Requests
0
Merged Pull Requests
32
Pull Request Acceptance Rate
100%
 Development
Primary Language
Ruby
Licenses
GPL-2.0-only
Average date of last 50 commits
2025-10-10
Reverse Dependencies
2

 Dependencies

Development

voxpupuli-rubocop
~> 5.1.0

Runtime

rake
~> 13.0
logger
< 2
 Project Readme

puppet_fixtures

Puppet module developers use a .fixtures.yml file to describe which resources to use during testing. This is a standalone implementation that improves puppetlabs_spec_helper by using better parallelization.

Usage

Add puppet_fixtures to your Gemfile:

gem 'puppet_fixtures'

Now you can use bundle exec puppet-fixtures, for example:

$ bundle exec puppet-fixtures show
Parsing .fixtures.yml

Symlinks
  /home/ekohl/dev/puppet-example/spec/fixtures/modules/example => /home/ekohl/dev/puppet-example

Repositories
  stdlib => git+https://github.com/puppetlabs/puppetlabs-stdlib

To install fixtures, run:

$ bundle exec puppet-fixtures install
I, [2025-05-08T13:14:33.084643 #79391]  INFO -- : Creating symlink /home/ekohl/dev/puppet-example/spec/fixtures/modules/example => /home/ekohl/dev/puppet-example
Cloning into '/home/ekohl/dev/puppet-example/spec/fixtures/modules/stdlib'...
remote: Enumerating objects: 472, done.
remote: Counting objects: 100% (472/472), done.
remote: Compressing objects: 100% (399/399), done.
remote: Total 472 (delta 99), reused 223 (delta 49), pack-reused 0 (from 0)
Receiving objects: 100% (472/472), 289.86 KiB | 7.07 MiB/s, done.
Resolving deltas: 100% (99/99), done.
$ bundle exec puppet-fixtures clean

Environment Variables

puppet_fixtures will parse environment variables and replace them in the .fixtures.yml file at runtime. This may leak sensitive information in logs, so be careful. But this is particularly useful for CI systems where you want to use private repositories.

For example, given the following .fixtures.yml:

fixtures:
  repositories:
    stdlib: https://github.com/puppetlabs/puppetlabs-stdlib
    mysql: https://ci-bot:${CI_JOB_TOKEN}@github.com/${CI_USER}/puppetlabs-mysql

Will replace ${CI_JOB_TOKEN} and ${CI_USER} with the values from the environment. But only when those variables are set.

$ export CI_USER=foobar
$ export CI_TOKEN=token.MC.T0ken_face
$ bundle exec puppet-fixtures show
Parsing .fixtures.yml

# ...

Repositories
  stdlib => git+https://github.com/puppetlabs/puppetlabs-stdlib
  mysql => git+https://ci-bot:token.MC.T0ken_face@github.com/foobar/puppetlabs-mysql

If you run this in GitLab CI, gitlab will mask the token in the logs. Because it is a default variable, you don't need to set it yourself. CI_USER is a custom variable, so you need to set it in your project/group settings. Or it will remain as ${CI_USER}.

$ bundle exec puppet-fixtures show
# ...
Parsing .fixtures.yml
Repositories
  stdlib => git+https://github.com/puppetlabs/puppetlabs-stdlib
  mysql => git+https://ci-bot:[MASKED]@github.com/${CI_USER}/puppetlabs-mysql