pdksync 0.5.0 → 0.8.0

data/README.md

@@ -4,12 +4,13 @@ Table of Contents
 -----------------
 
 1. [Overview](#overview)
-2. [Usage](#usage)
-3. [How it works](#how-it-works)
-4. [Configuration](#configuration)
-5. [Workflow](#workflow)
-6. [Migrating from modulesync to pdksync](#migrating-from-modulesync-to-pdksync)
-7. [Contributing](#contributing)
+2. [Requirements](#requirements)
+3. [Usage](#usage)
+4. [How it works](#how-it-works)
+5. [Configuration](#configuration)
+6. [Workflow](#workflow)
+7. [Migrating from modulesync to pdksync](#migrating-from-modulesync-to-pdksync)
+8. [Contributing](#contributing)
 
 ### Overview
 --------
@@ -18,10 +19,15 @@ Pdksync is an efficient way to run a `pdk update` command against the various Pu
 
 Pdksync by default expects that your Puppet module repositories live on GitHub and will behave accordingly. It also supports GitLab as an alternative Git hosting platform.
 
+### Requirements
+--------
+* Ruby >= 2.7
+* Bundler >= 1.15
+
 ### Usage
 ----------
 
-> Note: This tool creates a 'live' pull (merge) 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. Additionally make sure that the Pdksync configuration file `$HOME/.pdksync.yml` sets the correct namespace, Git platform and Git base URI for your modules. See section [Configuration](#configuration) for details.
+> Note: This tool creates a 'live' pull (merge) request against the main 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. Additionally make sure that the Pdksync configuration file `$HOME/.pdksync.yml` sets the correct namespace, Git platform and Git base URI for your modules. See section [Configuration](#configuration) for details.
 
 1. To use pdksync, clone the GitHub repo or install it as a gem. Set up the environment by exporting a GitHub token:
 
@@ -43,6 +49,35 @@ bundle install --path .bundle/gems/
 bundle exec rake pdksync
 ```
 
+### Github Token Permissions
+----------
+
+Follow the steps below to set up a Github token with the minimum level of permissions required by `pdksync`:
+
+- Log in to your Github account and navigate to the [Personal Access Tokens](https://github.com/settings/tokens) section under `Settings -> Developer settings`
+- Click [`Generate new token`](https://github.com/settings/tokens/new)
+- Select the check boxes appropriate for your use case below
+
+#### **Public Repos, No Workflow Modifications Permitted**
+
+- [ ] **repo**
+  - [ ] repo:status
+  - [ ] repo_deployment
+  - [x] public_repo
+  - [ ] repo:invite
+  - [ ] security_events
+- [ ] workflow  
+
+#### **Private Repos or Public Repos with Workflow Modifications Permitted**
+
+- [x] **repo**
+  - [x] repo:status
+  - [x] repo_deployment
+  - [x] public_repo
+  - [x] repo:invite
+  - [x] security_events
+- [x] workflow  
+
 ### How it works
 ------------
 
@@ -61,7 +96,7 @@ source "https://rubygems.org"
 
 git_source(:github) { |repo_name| "https://github.com/#{repo_name}" }
 
-gem 'pdksync', github: 'puppetlabs/pdksync', ref: 'pdksync-externalisation-fixes'
+gem 'pdksync'
 gem 'rake'
 ```
 
@@ -78,7 +113,7 @@ pdksync.yml:
 ```yaml
 ---
 namespace: 'YOUR GITHUB NAME'
-git_base_uri: 'git@github.com:'
+git_base_uri: 'git@github.com'
 ```
 
 
@@ -86,11 +121,66 @@ Run the following commands to check that everything is working as expected:
 
 ```shell
 bundle install --path .bundle/gems/
-bundle exec rake -T
 bundle exec rake git:clone_managed_modules
 ```
 
-The rake tasks take in a file, `managed_modules.yml`, stored within the local directory that lists all the repositories that need to be updated. It then clones them, one after another, so that a local copy exists. The `pdk 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. A pull request against master is opened, and pdksync begins to clone the next repository.
+pdksync tool is extended with the feature to update the Gemfile. Puppet provides a lot of useful gems to access and manage their functionality between modules. This functionality will help user to perform gem testing prior to release. User is given new rake tasks to update SHA/Version/Branch/line in the Gemfile. Then the changes can be committed, PR can be created which will run the acceptance tests in the PR. If all the tests are executing successfully then the user can close the PRS and release the gem. Below given are the workflows for doing module gem testing with pdksync.
+
+
+In Workflow 1 we can clone modules, update the gem file, create the commit, push the changes and create the PR using separate rake tasks.
+```shell
+bundle install --path .bundle/gems/
+bundle exec rake git:clone_managed_modules
+bundle exec rake 'pdksync:gem_file_update[]'
+bundle exec rake 'git:create_commit[]'
+bundle exec rake 'git:push'
+bundle exec rake 'git:create_pr[]'
+```
+
+In Workflow 2 we can clone modules, update the gem file, create the commit, push the changes and create the PR using single rake task
+```
+Using single rake job
+bundle install --path .bundle/gems/
+bundle exec rake 'gem_testing[]'
+```
+
+In Workflow 3 we can clone modules, update the gem file, run the tests locally for litmus modules without creating commit,pushing or creating the PR
+```
+Using single rake job
+bundle install --path .bundle/gems/
+bundle exec rake git:clone_managed_modules
+bundle exec rake 'pdksync:gem_file_update[]'
+bundle exec rake 'pdksync:run_tests_locally[]'
+bundle exec rake 'pdksync:fetch_test_results_locally[]'
+```
+
+Once the verified gem is released we can use pdksync to update the the new version of gem released in the  .sync.yaml file.
+
+pdksync tool is extended with the feature to perform multi gem testing (`puppet-module-gems`). This functionality will identify the current version and bump the version by one. Then it will build and push the gems to gemfury account. Export the GEMFURY_TOKEN to use this rake task.
+
+ ```shell
+   export GEMFURY_TOKEN=<access_token>
+   ```
+
+Run the following commands to check that everything is working as expected:
+
+```shell
+bundle install --path .bundle/gems/
+bundle exec rake -D
+bundle exec rake 'git:clone_gem['gem_name']'
+```
+Below given are the workflows for doing multi gem testing with pdksync.
+
+In this workflow we can clone gems, update the version, build the gem, push the changes to gemfury and update the gem file of the required modules with the latest gem updated in the fury. Then we can create PR or run tests locally or run tests through jenkins to verify the module test results.
+
+```shell
+bundle install --path .bundle/gems/
+bundle exec rake 'git:clone_gem[]'
+bundle exec rake 'pdksync:multi_gem_testing[]'
+bundle exec rake 'pdksync:multigem_file_update[]'
+```
+
+The rake tasks take in a file, `managed_modules.yml`, stored within the local directory that lists all the repositories that need to be updated. It then clones them, one after another, so that a local copy exists. The `pdk 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 origin — where the local copy was originally cloned. A pull request against main is opened, and pdksync begins to clone the next repository.
 
 By default, pdksync will supply a label to a PR (default is 'maintenance'). This can be changed by creating `pdksync.yml` in the local directory and setting the `pdksync_label` key. You must ensure that the label selected exists on the modules that you are applying pdksync to. Should you wish to disable this feature, set `pdksync_label` to an empty string i.e. `''`. Similarly, when supplying a label using the `git:create_pr` rake task, the label must exist on each of the managed modules to run successfully.
 
@@ -104,9 +194,163 @@ The following rake tasks are available with pdksync:
 - `pdksync:pdk_convert` Runs PDK convert against modules.
 - `pdksync: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`
-- `pdksync:run_a_command[:command]` Run a command against modules eg rake 'pdksync:run_a_command[complex command here -f -gx]'
+  - `rake pdksync` PR title outputs as `pdksync - pdksync_heads/main-0-gabccfb1`
+  - `rake 'pdksync[MODULES-8231]'` PR title outputs as `pdksync - MODULES-8231 - pdksync_heads/main-0-gabccfb1`
+- `pdksync:run_a_command[:command, :option]` Run a command against modules eg rake 'pdksync:run_a_command[complex command here -f -gx, 'background']'. :option is an optional parameter which states to run command in backgroud.
+- `pdksync:gem_file_update[[:gem_to_test, :gem_line, :gem_sha_finder, :gem_sha_replacer, :gem_version_finder, :gem_version_replacer, :gem_branch_finder, :gem_branch_replacer]]` Run gem_file_update against modules
+  - eg rake to update gem line `pdksync:gem_file_update['puppet_litmus', "gem 'puppet_litmus'\, git: 'https://github.com/test/puppet_litmus.git'\, branch: 'testbranch'"]'`
+  - eg rake to update sha `pdksync:gem_file_update['puppet_litmus', '', '20ee04ba1234e9e83eb2ffb5056e23d641c7a018', '20ee04ba1234e9e83eb2ffb5056e23d641c7a31']`
+  - eg rake to update version`pdksync:gem_file_update['puppet_litmus', '', '', '', "= 0.9.0", "<= 0.10.0", '', '']`
+  - eg rake to update branch `pdksync:gem_file_update['puppet_litmus', '', '', '', '', '', 'testbranch', 'testbranches']`
+- `rake 'gem_testing[:additional_title, :gem_to_test, :gem_line, :gem_sha_finder, :gem_sha_replacer, :gem_version_finder, :gem_version_replacer, :gem_branch_finder, :gem_branch_replacer]'` Run complete Gem file testing (cloning, gemfileupdate, create commit, create PR)PR title outputs as `pdksync_gemtesting - MODULES-8231 - pdksync_heads/main-0-gabccfb1`
+  - eg rake to perform gem file testing `gem_testing['MODULES-testing', 'puppet_litmus', '', '20ee04ba1234e9e83eb2ffb5056e23d641c7a018', 'testsha']`
+- `pdksync:run_tests_locally[:provision_type, :puppet_collection]` Run litmus modules locally
+  - eg rake 'pdksync:run_tests_locally["default"]'
+- `pdksync:fetch_test_results_locally[]` Fetch litmus modules local run results
+  - eg rake 'pdksync:fetch_test_results_locally[]'
+- `pdksync:run_tests_jenkins[:jenkins_server_url, :github_branch, :test_framework, :github_user]` Run traditional modules on jenkins. For now this rake task works just for test_framework: jenkins.
+  - eg rake 'pdksync:run_tests_jenkins[test_branch, '', test_user]'
+- `pdksync:test_results_jenkins[]` Fetch traditional modules jenkins run results
+  - eg rake 'pdksync:test_results_jenkins[jenkins_server_url]'
+- `git:clone_gem[:gem_name]` Clone gem.
+- `pdksync:multi_gem_testing[:gem_name, :version_file, :build_gem, :gem_path, :gemfury_username]` Build and Push new gems built to the gemfury account for testing eg rake 'pdksync:multi_gem_testing[]'
+- `pdksync:multigem_file_update[:gem_name, :gemfury_username]` Update Gemfile of the modules with the new gem should be pushed to Gemfury.'
+- `pdksync:add_provision_list[:key, :provisioner, :images]` Add a provision list key to provision.yaml.
+- `pdksync:generate_vmpooler_release_checks[:puppet_version]` Generates release checks in provision.yaml based on module compatible platforms and puppet version
+- `pdksync:add_platform_to_metadata[:os, :version]` Add a given OS Version to the metadata
+- `pdksync:remove_platform_from_metadata[:os, :version]` Remove a given OS Version from the metadata
+
+
+You can run ```bundle exec rake -D``` to view the list of available rake tasks.
+
+### Adding/Updating `provision.yaml`
+To add/update an entry in the `provision.yaml`, run the following task:
+```ruby
+bundle exec rake pdksync:add_provision_list[:key, :provisioner, :images]
+```
+The `:images` parameter is a variable in length - everything from the 3rd arg onwards, separated by commas, will be treated as an image.
+For example:
+```ruby
+bundle exec rake "pdksync:add_provision_list[release_checks_latest_os, abs, 'redhat-8-x86_64', 'centos-8-x86_64', 'debian-10-x86_64', 'sles-15-x86_64', 'ubuntu-2004-x86_64', 'win-2019-core-x86_64', 'win-10-pro-x86_64']"
+```
+This will create a new entry (or update an existing entry, if it already exists) in the `provision.yaml`:
+```yaml
+release_checks_latest_os:
+    provisioner: abs
+    images:
+    - redhat-8-x86_64
+    - centos-8-x86_64
+    - debian-10-x86_64
+    - sles-15-x86_64
+    - ubuntu-2004-x86_64
+    - win-2019-core-x86_64
+    - win-10-pro-x86_64
+```
+
+### Generating Release Checks Config in `provision.yaml` for Given Puppet Version
+To generate a release checks configuration that will use VMPooler (via the ABS provisioner) in the `provision.yaml` that satisfies both:
+- The supported platforms of the given Puppet version
+- The supported platforms of the module
+
+...you can run:
+```ruby
+pdksync:generate_vmpooler_release_checks[:puppet_version]
+```
+
+#### Step 1: Create Puppet version supported platform config entry
+Ensure that the there is an entry in the `lib/pdksync/conf/puppet_abs_support_platforms.yaml` config for the Puppet version you wish to add an entry for:
+```yaml
+7:
+  centos: ['7', '8']
+  debian: ['9', '10']
+  oracle: ['7']
+  redhat: ['7', '8']
+  sles: ['12', '15']
+  scientific: ['7']
+  ubuntu: ['18.04', '20.04']
+  win: ['2012r2', '2016-core', '2019-core', '10']
+```
+**NOTE: Please be aware of the requirements regarding the platform naming and version syntax. Instructions and an explanation are within the `puppet_support_platforms.yaml`**
+
+The platforms specified above do not necessarily have to reflect ALL the platforms that Puppet version supports - this is the configuration we wish to test against.
+If you do not wish to test against `solaris` then simply omit it from the above config.
+
+#### Step 2: Add the config entries to `provision.yaml`
+Say you want to add a configuration key for Puppet 7 (_and you have ensured the `puppet_support_platforms.yaml` is correct as defined in the step above_), you would run:
+```ruby
+bundle exec rake 'pdksync:generate_vmpooler_release_checks[7]'
+```
+This will create a `release_checks_7` entry in the `provision.yaml` of the managed modules cloned down that contains a list of appropriate number of platforms to satisfy the conditions outlined above.
+
+### Adding a new platform to `metadata.json`
+
+To add a new OS or OS version to the `operatingsystem_support` key in the `metadata.json`:
+
+```ruby
+bundle exec rake 'pdksync:add_platform_to_metadata[:os, :version]'
+```
+
+For example, to add a new OS called 'FooBar OS' and versions `1`, `2` and `3`:
+
+```ruby
+bundle exec rake 'pdksync:add_platform_to_metadata[FooBar,1]'
+bundle exec rake 'pdksync:add_platform_to_metadata[FooBar,2]'
+bundle exec rake 'pdksync:add_platform_to_metadata[FooBar,3]'
+```
+
+To add a new version (e.g. `22.04`) to an existing entry (e.g. `Ubuntu`):
+
+```ruby
+bundle exec rake 'pdksync:add_platform_to_metadata[Ubuntu,22.04]'
+```
+
+**PLEASE NOTE: All OS names are normalised to the conventions defined in the `normalize_os` method - see below for more details.**
+
+### Removing a platform from `metadata.json`
+
+To remove a platform version from `metadata.json`:
+
+```ruby
+bundle exec rake 'pdksync:remove_platform_from_metadata[:os, :version]'
+```
+
+**PLEASE NOTE: There is currently a limitation on removing an entire OS if no versions are specified - feel free to enhance with a PR :)**
+
+For example, to remove version `14.04` from `Ubuntu`:
+
+```ruby
+bundle exec rake 'pdksync:remove_platform_from_metadata[Ubuntu,14.04]'
+```
+
+### Update requirements
+
+To add / modify a requirement from the `requirements` key of the `metadata.json`:
+
+```ruby
+bundle exec rake 'pdksync:update_requirements[:name, :key, :value]'
+```
+
+**PLEASE NOTE: There is currently a limitation on removing an entire requirement entry - feel free to enhance with a PR :)**
+
+To update the `puppet` `version_requirement` requirement to `>= 6.0.0 < 8.0.0`:
+
+```ruby
+bundle exec rake 'pdksync:update_requirements[puppet,version_requirement,>= 6.0.0 < 8.0.0]'
+```
+
+To add a new requirement called `foobar` with a parameter called `baz` which has a value of `123`:
+
+```ruby
+bundle exec rake 'pdksync:update_requirements[foobar,baz,123]'
+```
+
+### Normalize Supported Platforms
+
+To normalize the platforms and versions (Windows only) defined in the `operatingsystem_support` key of the `metadata.json` based on [these rules](https://github.com/puppetlabs/pdksync/blob/ebb84d81d2c15115f896995043eac6d666a114a0/lib/pdksync/utils.rb#L1043-L1098):
+
+```ruby
+bundle exec rake 'pdksync:normalize_metadata_supported_platforms'
+```
 
 ### Configuration
 
@@ -115,8 +359,9 @@ By default pdksync will use hardcoded values for configuring itself. However, if
 ---
 namespace: 'puppetlabs'
 pdksync_dir: 'modules_pdksync'
+pdksync_gem_dir: 'gems_pdksync',
 push_file_destination: 'origin'
-create_pr_against: 'master'
+create_pr_against: 'main'
 managed_modules: 'managed_modules.yml'
 pdksync_label: 'maintenance'
 git_platform: :github
@@ -134,8 +379,14 @@ By default pdksync assumes you are hosting your Puppet modules on GitHub, and Gi
 Pdksync also supports the GitLab platform, but without official support by Puppetlabs.
 
 ##### GitHub
+Github.com and Github enterprise both work with octokit which is used in pdksync.  There are some settings
+you will need to adjust if using the on premise github enterprise edition.
 
-To use GitHub you only need to export your GitHub access token as the
+1. `api_endpoint: https://mygithub.mycompany.com/api/v3`
+2. `git_base_uri: git@mygithub.mycompany.com`
+3. `export GITHUB_TOKEN=k3939isdiasdf93i_`  (your token goes here)
+
+To use GitHub.com you only need to export your GitHub access token as the
 environment variable `GITHUB_TOKEN` and configure the namespace in which your
 modules are hosted in `$HOME/.pdksync.yml` as described above.
 
@@ -163,7 +414,7 @@ export GITLAB_TOKEN=<your GitLab access token here>
 
 If you are running your own GitLab instance on premise or use a GitLab instance
 other than the official one at `https://gitlab.com` you also need to configure
-`git_base_uri` and `gitlab_api_endpoint` in `$HOME/.pdksync.yml` so that
+`git_base_uri` and `api_endpoint` in `$HOME/.pdksync.yml` so that
 pdksync knows from where to clone your modules and where to access to GitLab
 API to create the live merge requests:
 
@@ -175,9 +426,70 @@ git_platform: :gitlab
 git_base_uri: 'https://gitlab.example.com'
 # alternatively use SSH:
 #git_base_uri: 'ssh://git@gitlab.example.com:2222'
-gitlab_api_endpoint: 'https://gitlab.example.com/api/v4'
+api_endpoint: 'https://gitlab.example.com/api/v4'
+```
+
+### Setting who has the authoritive
+It may be desirable to allow modules to dictate which version of the pdk-templates they should sync with.
+There are a few settings you can tune to allow for this kind of flexability.  These settings are in the pdksync.yml file.  All of these settings are optional and have sane defaults.  See `rake pdksync:show_config` for the settings that will be used.
+
+- pdk_templates_prefix: 'nwops-'  (example only, keep as empty string)
+- pdk_templates_ref: 1.12.0
+- pdk_templates_url: https://github.com/puppetlabs/pdk-templates.git
+- module_is_authoritive: true
+
+The first setting is `module_is_authoritive`.  When this is set to true the templates and ref specified in the metadata become the authoritive source for these settings.  Even if you have pdk_templates_ref and pdk_templates_url specified in pdksync.yml the metadata settings will alwasys be used.
+
+```json
+# module/metadata.json
+{
+"pdk-version": "1.11.1",
+"template-url": "https://github.com/puppetlabs/pdk-templates#main",
+"template-ref": "heads/main-0-gb096033"
+}
+
 ```
 
+When `module_is_authoritive` is set to false the pdk_templates_ref and pdk_templates_url will override what is found in the modules's metadata.json file.  This is very useful when you have to control pdk-template upgrades on modules.
+
+The other settings dictiate where the templates are located and which branch, tag or reference you want to use.
+`pdk_templates_ref: 'main'` and `pdk_templates_url: https://github.com/puppetlabs/pdk-templates.git`.  These settings will only be utilized if module_is_authoritive is set to false.  However, if you are performing a conversion via pdksync these settings will also be used since the metadata in the module being converted doesn't have pdk settings yet.
+
+The last setting `pdk_templates_prefix` is a special use case that allows folks with internal forks of pdk-templates to keep branches of the pdk-template tags with additional custom changes. Setting this to an empty string disables this.  You will most likely need to resolve conflicts with this workflow, so it is not for everyone.  If you know of a better way please submmit a pull request.
+
+This strategy works in conjunction with the pdk-template git tags and the workflow looks like:
+  1. git fetch upstream (github.com/puppetlabs/pdk-templates)
+  2. git checkout main && git rebase upstream/main
+  3. git checkout -b nwops-1.0.13 nwops-1.0.12
+  4. git rebase 1.0.13
+  5. git push origin nwops-1.0.13
+
+
+### Supporting multiple namespaces
+If you have multiple namespaces that you need to support you will need to create a pdksync.yml config
+file for each namespace.  This will allow you to create a folder structure and keep a separate
+managed_modules.yml for that namespace too.
+
+You can set a PDKSYNC_CONFIG_PATH environment variable that points to the specific pdksync.yml config file for use in a CI or on the CLI. This allows you to set custom names for pdksync.yml file.
+
+example: `PDKSYNC_CONFIG_PATH=pdksync_ops.yml`
+
+Or you can set a different HOME environment variable that tells pdksync where to find the pdksync.yml file.  Pdksync will locate the pdksync.yml file in the HOME folder you specify.  The config file name is not changable in this case.
+
+example: `HOME=ops`
+
+### Logging output
+Pdksync uses a logger class to log all output.  You can control how the logger works via a few environment variables.
+
+To control the level set the `LOG_LEVEL` to one of
+1. info
+2. debug
+3. fatal
+4. error
+5. warn
+
+To control where the logs are sent (defaults to stdout) set the `PDKSYNC_LOG_FILENAME` to a file path.
+
 ### Workflow
 --------
 

data/Rakefile

@@ -1,33 +1,12 @@
-require 'pdksync/rake_tasks'
-require 'github_changelog_generator/task'
-require 'rubocop/rake_task'
+require "pdksync/rake_tasks"
+require "rubocop/rake_task"
+require "rspec/core/rake_task"
+require "bundler/gem_tasks"
 
 RuboCop::RakeTask.new(:rubocop) do |t|
-  t.options = ['--display-cop-names']
+  t.options = ["--display-cop-names"]
 end
 
-GitHubChangelogGenerator::RakeTask.new :changelog do |config|
-  config.user = 'puppetlabs'
-  config.project = 'pdksync'
-  # config.since_tag = '1.1.1'
-  config.future_release = '0.5.0'
-  config.exclude_labels = ['maintenance']
-  config.header = "# Change log\n\nAll notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) and this project adheres to [Semantic Versioning](http://semver.org)."
-  config.add_pr_wo_labels = true
-  config.issues = false
-  config.merge_prefix = "### UNCATEGORIZED PRS; GO LABEL THEM"
-  config.configure_sections = {
-    "Changed" => {
-      "prefix" => "### Changed",
-      "labels" => ["backwards-incompatible"],
-    },
-    "Added" => {
-      "prefix" => "### Added",
-      "labels" => ["feature", "enhancement"],
-    },
-    "Fixed" => {
-      "prefix" => "### Fixed",
-      "labels" => ["bugfix"],
-    },
-  }
-end
+RSpec::Core::RakeTask.new(:spec)
+
+task :default => :spec

data/lib/pdksync/conf/puppet_abs_supported_platforms.yaml

@@ -0,0 +1,41 @@
+# PUPPET VERSION PLATFORM COMPATIBILITY
+#
+# Define the Puppet version as a root key, then specify the OS platform(s) and versions(s) that this Puppet version is
+# compatible with AND that you wish to test on. If you wish to exclude a platform from testing, simply omit it.
+#
+# OS names and versions must conform to the VMPooler nomenclature and conventions.
+#
+# Running 'bundle exec rake 'pdksync:generate_vmpooler_release_checks[7]' will generate an entry in the 'provision.yaml'
+# for each managed module that contains a configuration that satisfies both:
+# - The module's compatible platforms
+# - The Puppet version's compatible platforms (in this example: '7')
+#
+# NOTE: arch will always be assumed to be 'x86_64'
+---
+5:
+  centos: ['5', '6', '7', '8']
+  debian: ['8', '9', '10']
+  oracle: ['5', '6', '7']
+  redhat: ['5', '6', '7', '8']
+  sles: ['12', '15']
+  scientific: ['6', '7']
+  ubuntu: ['14.04', '16.04', '18.04']
+  win: ['2008r2', '2012r2', '2016', '2019', '10-pro']
+6:
+  centos: ['5', '6', '7', '8']
+  debian: ['8', '9', '10']
+  oracle: ['5', '6', '7']
+  redhat: ['5', '6', '7', '8']
+  sles: ['12', '15']
+  scientific: ['6', '7']
+  ubuntu: ['14.04', '16.04', '18.04', '20.04']
+  win: ['2008r2', '2012r2', '2016', '2019', '10-pro']
+7:
+  centos: ['7', '8']
+  debian: ['9', '10']
+  oracle: ['7']
+  redhat: ['7', '8']
+  sles: ['12', '15']
+  scientific: ['7']
+  ubuntu: ['18.04', '20.04']
+  win: ['2012r2', '2016', '2019', '10-pro']

data/lib/pdksync/configuration.rb

@@ -0,0 +1,155 @@
+require 'yaml'
+require 'pdk/version'
+require 'ostruct'
+
+# @summary
+#   A class used to contain a set of configuration variables
+# @note
+#   Configuration is loaded from `$HOME/.pdksync.yml`. If $HOME is not set, the config_path will use the current directory.
+#   The configuration filename and path can be overridden with env variable PDK_CONFIG_PATH
+#   Set PDKSYNC_LABEL to '' to disable adding a label during pdksync runs.
+module PdkSync
+  class Configuration < OpenStruct
+    SUPPORTED_SCM_PLATFORMS = [:github, :gitlab].freeze
+    PDKSYNC_FILE_NAME = 'pdksync.yml'.freeze
+
+    # Any key value added to the default config or custom config
+    # will automatically be a new configuration item and referenced
+    # via Configuration.new.<key_name> ie.
+    # c = Configuration.new
+    # c.api_endpoint
+    DEFAULT_CONFIG = {
+      namespace: 'puppetlabs',
+      pdksync_dir: 'modules_pdksync',
+      pdksync_gem_dir: 'gems_pdksync',
+      push_file_destination: 'origin',
+      create_pr_against: 'main',
+      managed_modules: 'managed_modules.yml',
+      pdksync_label: 'maintenance',
+      git_platform: :github,
+      git_base_uri: 'https://github.com',
+      gitlab_api_endpoint: 'https://gitlab.com/api/v4',
+      api_endpoint: nil,
+      pdk_templates_prefix: nil,
+      pdk_templates_ref: PDK::VERSION,
+      pdk_templates_url: 'https://github.com/puppetlabs/pdk-templates.git',
+      jenkins_platform: :jenkins,
+      jenkins_base_uri: 'https://jenkins.io',
+      jenkins_api_endpoint: '',
+      jenkins_server_url: '',
+      module_is_authoritive: true
+    }.freeze
+
+    # @param config_path [String] -  the path to the pdk config file
+    def initialize(config_path = ENV['PDKSYNC_CONFIG_PATH'])
+      @config_path = locate_config_path(config_path)
+      @custom_config = DEFAULT_CONFIG.merge(custom_config(@config_path))
+      @custom_config[:pdk_templates_ref] = "#{@custom_config[:pdk_templates_prefix]}#{@custom_config[:pdk_templates_ref]}"
+      super(@custom_config)
+      valid_scm?(git_platform)
+      valid_access_token?
+    end
+
+    # @return [Hash] - returns the access settings for git scm
+    def git_platform_access_settings
+      @git_platform_access_settings ||= {
+        access_token: access_token,
+        gitlab_api_endpoint: gitlab_api_endpoint || api_endpoint,
+        api_endpoint: api_endpoint
+
+      }
+    end
+
+    def jenkins_platform_access_settings
+      @jenkins_platform_access_settings ||= {
+        jenkins_username: ENV['JENKINS_USERNAME'].freeze,
+        jenkins_password: ENV['JENKINS_PASSWORD'].freeze,
+        jenkins_api_endpoint: ''
+      }
+    end
+
+    # @return [Hash] - returns the access settings for gemfury account
+    def gemfury_access_settings
+      valid_access_token_gem_fury?
+      @gemfury_access_token = access_token_gem_fury
+    end
+
+    # @return [String] return a rendered string for pdk to use the templates
+    def templates
+      "--template-url=#{pdk_templates_url} --template-ref=#{pdk_templates_ref}"
+    end
+
+    # @param path [String] path to the pdksync config file in yaml format
+    # @return [Hash] the custom configuration as a hash
+    def custom_config(path = nil)
+      return {} unless path
+      return {} unless File.exist?(path)
+      c = (YAML.load_file(path) || {}).transform_keys_to_symbols
+      c[:git_base_uri] ||= 'https://gitlab.com' if c[:git_platform].eql?(:gitlab)
+      c
+    end
+
+    # @return [String] the path the pdksync config file, nil if not found
+    def locate_config_path(custom_file = nil)
+      files = [
+        custom_file,
+        PDKSYNC_FILE_NAME,
+        File.join(ENV['HOME'], PDKSYNC_FILE_NAME)
+      ]
+      files.find { |file| file && File.exist?(file) }
+    end
+
+    private
+
+    # @return [Boolean] true if the supported platforms were specified correctly
+    # @param scm [Symbol] - the scm type (:github or :gitlab)
+    def valid_scm?(scm)
+      unless SUPPORTED_SCM_PLATFORMS.include?(scm)
+        raise ArgumentError, "Unsupported Git hosting platform '#{scm}'."\
+          " Supported platforms are: #{SUPPORTED_SCM_PLATFORMS.join(', ')}"
+      end
+      true
+    end
+
+    # @return [Boolean] true if the access token for the scm platform was supplied
+    def valid_access_token?
+      if access_token.nil?
+        raise ArgumentError, "Git platform access token for #{git_platform.capitalize} not set"\
+          " - use 'export #{git_platform.upcase}_TOKEN=\"<your token>\"' to set"
+      end
+      true
+    end
+
+    # @return [Boolean] true if the access token for the gemfury was supplied
+    def valid_access_token_gem_fury?
+      if access_token_gem_fury.nil?
+        raise 'Gemfury access token not set'\
+        " - use 'export GEMFURY_TOKEN=\"<your token>\"' to set"
+      end
+      true
+    end
+
+    # @return [String] the platform specific access token
+    def access_token
+      case git_platform
+      when :github
+        ENV['GITHUB_TOKEN'].freeze
+      when :gitlab
+        ENV['GITLAB_TOKEN'].freeze
+      end
+    end
+
+    # @return [String] the gem_fury access token
+    def access_token_gem_fury
+      ENV['GEMFURY_TOKEN'].freeze
+    end
+  end
+end
+
+# monkey patch
+class Hash
+  # take keys of hash and transform those to a symbols
+  def transform_keys_to_symbols
+    each_with_object({}) { |(k, v), memo| memo[k.to_sym] = v; }
+  end
+end