Manage large sets of modules with automation built on top of PDK
Switch branches/tags
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
lib
spec/lib (MODULES-7695) - Add maintenance labels for PRs (#75) Nov 8, 2018
.gitignore (FEAT) add clone_managed_modules task, cleanup Aug 3, 2018
.rspec (maint) - Formatting test output Jun 28, 2018
.rubocop.yml (maint) - Rubocop Mar 29, 2018
.rubocop_todo.yml
.travis.yml (maint) adding github key for testing Aug 6, 2018
CHANGELOG.md Release Prep for 0.3.0 Nov 15, 2018
Gemfile (feat) add colourised output, fix pdk path Sep 24, 2018
LICENSE Addition of apache license May 14, 2018
README.md (MODULES-8231) - Add additional title info for pdksync runs Nov 9, 2018
Rakefile Release Prep for 0.3.0 Nov 15, 2018
managed_modules.yml Update managed_modules.yml Sep 26, 2018
pdksync.gemspec Release Prep for 0.3.0 Nov 15, 2018

README.md

Pdksync

Table of Contents

  1. Overview
  2. Usage
  3. How it works
  4. Installing
  5. Workflow
  6. Migrating from modulesync to pdksync
  7. Contributing

Overview


Pdksync is an efficient way to run a pdk update command against the various repositories that we manage — keeping them up-to-date with the changes made to PDK. It is a solution for converted modules that no longer run with modulesync.

Usage


Note: This tool creates a 'live' pull request against the master branch of the module it is running against — defined in managed_modules.yml. Before running this tool, ensure this file reflects the modules you wish it to run against, and that constants.rb is up-to-date with the correct namespace your modules reside in.

  1. To use pdksync, clone the GitHub repo or install it as a gem. Set up the environment by exporting a GitHub token:
export GITHUB_TOKEN=<access_token>
  1. Before the script will run, you need to install the gems:
bundle install --path .bundle/gems/
  1. Once this is complete, call the built-in rake task to run the module:
bundle exec rake pdksync

How it works


Pdksync is a gem that works to clone, update, and push module repositories. It is activated from within the pdksync module.

The gem takes in a file, managed_modules.yml, stored within the gem that lists all the repositories that need to be updated. It then clones them, one after another, so that a local copy exists. The update command is ran against this local copy, with the subsequent changes being added into a commit on a unique branch. It is then pushed back to the remote master — where the local copy was originally cloned. The commit is merged to the master via a pull request, causing the gem to begin to clone the next repository.

By default, pdksync will supply a label to a PR (default is 'maintenance'). This can be changed by opening lib/pdksync/constants.rb and modifying the PDKSYNC_LABEL constant. You must ensure that the label selected exists on the modules that you are applying pdksync to. Should you wish to disable this feature, simply change PDKSYNC_LABEL to an empty string i.e. ''. Similarly, when supplying a label using the git:push_and_create_pr rake task, the label must exist on each of the managed modules to run successfully.

The following rake tasks are available with pdksync:

  • git:clone_managed_modules Clone managed modules.
  • git:create_commit[:branch_name, :commit_message] Stage commits for modules, branchname and commit message eg rake 'git:create_commit[flippity, commit messagez]'.
  • git:push_and_create_pr[:pr_title, :label] Push commit, and create PR for modules. Label is optional eg rake 'git:push_and_create_pr[pr title goes here, optional label right here]'.
  • git:clean[:branch_name] Clean up origin branches, (branches must include pdksync in their name) eg rake 'git:clean[pdksync_origin_branch]'.
  • pdk:pdk_convert Runs PDK convert against modules.
  • pdk:pdk_validate Runs PDK validate against modules.
  • pdksync[:additional_title] Run full pdksync process, clone repository, pdk update, create pr. Additional information can be added to the title, which will be appended before the reference section.
    • rake pdksync PR title outputs as pdksync - pdksync_heads/master-0-gabccfb1
    • rake 'pdksync[MODULES-8231]' PR title outputs as pdksync - MODULES-8231 - pdksync_heads/master-0-gabccfb1
  • run_a_command[:command] Run a command against modules eg rake 'run_a_command[complex command here -f -gx]'

Workflow


It currently runs without additional arguments. To alter how it runs, make alterations to either the constants.rb or managed_modules.yml.

Managed modules


This module runs through a pre-set array of modules, with this array set within the managed_modules.yml file. This file makes use of a simple yaml style format to set out the different module names, for example:

---
- puppetlabs-motd
- puppetlabs-stdlib
- puppetlabs-mysql

To add a module, add it to the list. To remove a module, remove it from the list.

Migrating from modulesync to pdksync


If your modules are currently managed by modulesync, and you want to use PDK and keep your modules up-to-date, read the following.

Terminology

  • pdk convert - A command to convert your module, for example, to make it compatible with the PDK.
  • convert_report.txt - A report that shows the changes PDK will make to your module when pdk convert is ran.
  • pdk update - A command to consume any changes that have been made to the pdk-template used to convert the module.
  • update_report.txt - A report that shows the changes PDK will make to your module when pdk update is ran.
  • pdk validate - A command to run basic validation checks on your module.
  • pdk test unit - A command to run all available unit tests on your module.
  • .sync.yml - A file that lists all of of your module customizations — and will require work before module conversion.
Prerequisites
  • Unit tests are in a good state — with no failures. Check by running pdk test unit.
  • The module is in good shape. Check by running pdk validate.

When you're confident everything is in good shape, you can start converting your module to make it compatible with PDK.

Getting started
  1. Run pdk convert --noop. This will output to the console a high level overview of the changes that PDK is planning to make to your files.

Note: For an in-depth diff, see the convert_report.txt that is output in the module root directory.

  1. Make changes to your .sync.yml. State any configuration that the custom pdk-templates plan to remove.

Useful commands via the .sync.yml:

  • Add additional gem dependencies:
Gemfile:
  required:
    ':system_tests':
      - gem 'octokit'
        platforms: ruby
  • Make changes to your travis configuration:
.travis.yml:
  branches:
    - release
  • Delete files that you don't want to exist in the repo:
.gitlab-ci.yml:
  delete: true
  • Unmanage files that you don't want to be managed:
.gitlab-ci.yml:
  unmanaged: true

Note: It is unlikely your module will work out of the box.

  1. When you are finished customizing your .sync.yml file, run pdk convert --noop and confirm the changes that PDK will make when you convert. Changes can be found in the convert_report.txt

  2. Run pdk convert to convert. You will be prompted to pass in Y/N — type Y and all your changes will be applied.

Note: If you have any concerns it is not too late — type N.

  1. Run your unit tests to confirm that nothing has broken. If there are breakages, you might need to require a library or include a missing gem — address this issue before you continue.

  2. Run pdk validate to ensure there are no failures.

  3. Commit the changes that the pdk convert has made and create your pull request.

  4. Remove your module from being managed via modulesync, and start using pdksync going forward — no more manually creating pull requests.

For more information on keeping your module up to date with the PDK check out Helens blog post.

Compatibility


This tool has been developed and tested on OSX and Linux. It currently does not run on Windows.

Contributing


  1. Fork the repo
  2. Create your feature branch:
git checkout -b my-new-feature
  1. Commit your changes:
git commit -am 'Add some feature'
  1. Push to the branch:
git push origin my-new-feature
  1. Create a new pull request