Add Dockerfile and GitHub actions for CI/releases

.github/dependabot.yml

@@ -0,0 +1,14 @@
+version: 2
+updates:
+- package-ecosystem: "github-actions"
+  directory: "/"
+  schedule:
+    interval: "daily"
+- package-ecosystem: "docker"
+  directory: "/"
+  schedule:
+    interval: "daily"
+- package-ecosystem: "bundler"
+  directory: "/"
+  schedule:
+    interval: "daily"

.github/workflows/ci.yml

@@ -0,0 +1,24 @@
+name: "Run CI"
+
+on:
+  push:
+    branches: ["production"]
+  pull_request:
+  workflow_call:
+
+jobs:
+  test:
+    runs-on: "ubuntu-latest"
+    strategy:
+      matrix:
+        task:
+        - "spec"
+        - "lint"
+        - "metadata_lint"
+        - "syntax"
+        - "rubocop"
+    steps:
+    - uses: "actions/checkout@v4"
+    - name: "rake ${{ matrix.task }}"
+      run: |
+        docker run --rm `docker build -q .` rake ${{ matrix.task }}

.github/workflows/release.yml

@@ -0,0 +1,37 @@
+name: "Release to Puppet Forge"
+
+on: "workflow_dispatch"
+
+jobs:
+  test:
+    uses: "./.github/workflows/ci.yml"
+
+  release:
+    runs-on: "ubuntu-latest"
+    needs: "test"
+    steps:
+    - uses: "actions/checkout@v4"
+    - name: "get version"
+      id: "get_version"
+      run: |
+        echo "version=`jq --raw-output .version metadata.json`" >> $GITHUB_OUTPUT
+    - name: "pdk build"
+      uses: "docker://puppet/pdk:3.0.0.0"
+      with:
+        args: "build"
+    - name: "gh changelog get --latest"
+      run: |
+        export GH_HOST=github.com
+        gh extension install chelnak/gh-changelog
+        gh changelog get --latest > OUTPUT.md
+      env:
+        GH_TOKEN: "${{ secrets.GITHUB_TOKEN }}"
+    - name: "gh release create"
+      run: |
+        gh release create v${{ steps.get_version.outputs.version }} --title v${{ steps.get_version.outputs.version }} -F OUTPUT.md
+      env:
+        GH_TOKEN: "${{ secrets.GITHUB_TOKEN }}"
+    - name: "pdk publish"
+      uses: "docker://puppet/pdk:3.0.0.0"
+      with:
+        args: "release publish --forge-token ${{ secrets.FORGE_API_KEY }} --force"

CHANGELOG.md

@@ -8,7 +8,7 @@ to [Semantic Versioning][2].
 [1]: https://keepachangelog.com/en/1.1.0/
 [2]: https://semver.org/spec/v2.0.0.html
 
-## [0.1.0](https://github.com/mlibrary/puppet-$FORGE_MODULE_NAME/tree/v0.1.0) - YYYY-mm-dd
+## [0.1.0](https://github.com/mlibrary/puppet-forge_module_name/tree/v0.1.0) - YYYY-mm-dd
 
 ### Added
 

Dockerfile

@@ -0,0 +1,8 @@
+FROM ruby:3.3
+RUN gem install bundler && mkdir -p /usr/src/app
+COPY Gemfile* /usr/src/app
+WORKDIR /usr/src/app
+RUN bundle install
+COPY . /usr/src/app
+ENTRYPOINT ["bundle", "exec"]
+CMD ["rake", "spec"]

README.md

@@ -1,4 +1,4 @@
-# FORGE_MODULE_NAME
+# forge_module_name
 
 Welcome to your new module. A short overview of the generated parts can be found
 in the [PDK documentation][1].
@@ -9,10 +9,10 @@ information to include in your README.
 ## Table of Contents
 
 1. [Description](#description)
-1. [Setup - The basics of getting started with FORGE_MODULE_NAME](#setup)
-    * [What FORGE_MODULE_NAME affects](#what-FORGE_MODULE_NAME-affects)
+1. [Setup - The basics of getting started with forge_module_name](#setup)
+    * [What forge_module_name affects](#what-forge_module_name-affects)
     * [Setup requirements](#setup-requirements)
-    * [Beginning with FORGE_MODULE_NAME](#beginning-with-FORGE_MODULE_NAME)
+    * [Beginning with forge_module_name](#beginning-with-forge_module_name)
 1. [Usage - Configuration options and additional functionality](#usage)
 1. [Limitations - OS compatibility, etc.](#limitations)
 1. [Development - Guide for contributing to the module](#development)
@@ -27,7 +27,7 @@ is what they want.
 
 ## Setup
 
-### What FORGE_MODULE_NAME affects **OPTIONAL**
+### What forge_module_name affects **OPTIONAL**
 
 If it's obvious what your module touches, you can skip this section. For
 example, folks can probably figure out that your mysql_instance module affects
@@ -49,7 +49,7 @@ another module, etc.), mention it here.
 If your most recent release breaks compatibility or requires particular steps
 for upgrading, you might want to include an additional "Upgrading" section here.
 
-### Beginning with FORGE_MODULE_NAME
+### Beginning with forge_module_name
 
 The very basic steps needed for a user to get the module up and running. This
 can include setup steps, if necessary, or it can be an example of the most basic

metadata.json

@@ -1,10 +1,10 @@
 {
-  "name": "mlibrary-$FORGE_MODULE_NAME",
+  "name": "mlibrary-forge_module_name",
   "version": "0.1.0",
   "author": "Regents of the University of Michigan",
   "summary": "",
   "license": "BSD-3-Clause",
-  "source": "https://github.com/mlibrary/puppet-$FORGE_MODULE_NAME",
+  "source": "https://github.com/mlibrary/puppet-forge_module_name",
   "dependencies": [
 
   ],

spec/spec_helper.rb

@@ -18,7 +18,7 @@
 
 default_fact_files = [
   File.expand_path(File.join(File.dirname(__FILE__), 'default_facts.yml')),
-  File.expand_path(File.join(File.dirname(__FILE__), 'default_module_facts.yml')),
+  File.expand_path(File.join(File.dirname(__FILE__), 'default_module_facts.yml'))
 ]
 
 default_fact_files.each do |f|
@@ -53,7 +53,7 @@
   # Filter backtrace noise
   backtrace_exclusion_patterns = [
     %r{spec_helper},
-    %r{gems},
+    %r{gems}
   ]
 
   if c.respond_to?(:backtrace_exclusion_patterns)