| Age | Commit message (Collapse) | Author |
|---|
|
Remove Litmus from Gemfile
|
|
We do not use Litmus for tests and its dependencies are causing issues
in our CI pipeline. This commit removes Litmus from the Gemfile.
|
|
(PA-6139) Drop beaker-puppet_install_helper gem in mailalias-core module
|
|
|
|
Beaker bump and PDK update
|
|
|
|
|
|
Release prep v1.2.0
|
|
|
|
(PA-6178) Use PDK template 3.0.1, Beaker 5, and newer module release workflow
|
|
Previously, when running with beaker 5 and latest beaker-puppet, tests failed
with:
cannot add defaults of type pe for host redhat7-64-1 (add_pe_defaults_on not present)
The error came from beaker-puppet when it tried to configure the host as a PE
agent[1].
The root cause is beaker defaults its options to `pe`[2]. When `beaker-puppet`
calls the `configure_type_defaults_on` method, it calls the appropriate
`add_<type>_defaults_on` method. This works when using beaker 4 as `beaker-pe`
is pulled in as a dependency and its `add_pe_defaults_on` method[3] is included
into the tests.
However, when running with beaker5, beaker-pe is not loaded, so the method is
undefined. It appears beaker-puppet_install_helper is responsible for the
whether beaker-pe is loaded or not, but only when using
beaker-puppet_install_helper 0.9.4.
Since these tests don't actually depend on PE, drop beaker-pe, require
'beaker-puppet' directly (so the install_from_build_data_url method exists) and
configure the host type directly.
[1] https://github.com/puppetlabs/beaker-puppet/blob/7175b5c1acb5cddb3a31ddcc114f09cddd3b83d0/lib/beaker-puppet/install_utils/puppet_utils.rb#L167
[2] https://github.com/voxpupuli/beaker/blob/c61ee381d3801bad70989d9b3cbf970771e6f330/lib/beaker/options/presets.rb#L139
[3] https://github.com/puppetlabs/beaker-pe/blob/3bfe913b8d57c805cc0c51ae899fff174224d5f5/lib/beaker-pe/install/pe_defaults.rb#L93
|
|
This commit updates .sync.yml and Gemfile to use Beaker 5.x, beaker-abs 1.x,
beaker-puppet 3.x and drops beaker-pe. Also, this commit adds a condition for
beaker-puppet to ensure beaker-puppet is only listed in the Gemfile if Ruby is
< 3.1.0. This is because beaker-puppet cannot run on Ruby > 3.1 or else Bundler
errors will occur.
|
|
This commit updates this module from PDK template 2.7.1 to 3.0.1 and updates
the module release workflows to use the newer release_prep instead of
auto_release GitHub Action wofklow. This commit also:
- Removes the github_changelog_generator and concurrent-ruby gems because they
are no longer needed for the new module release process in PDK template
- Updates the Rakefile to use Vox Rake tasks only if the vospupuli-acceptance
gem is installed
|
|
Actions and test updates
|
|
This commit updates the static code analysis GitHub Actions workflow
from using a copy in this repository to a resuable copy in the Phoenix
team centralized GitHub Actions repository.
In addition, this removes the commits Rake task as it is no longer used
in the reusable version of this workflow.
|
|
|
|
This commit adds a GitHub Actions workflow to export issues from GitHub
into Jira.
|
|
Previously in Beaker, you could use a standalone stdout method to
access output from remote machines.
This was deprecated in 2013 with voxpupuli/beaker@28b2510 and dropped
entirely in voxpupuli/beaker@73a31c7.
This commit replaces stdout in favor of calling stdout on Result
objects.
|
|
The assert_no_match method in Beaker was long deprecated then eventually
removed altogether in voxpupuli/beaker@6282311
This commit updates assert_no_match to refute_match.
|
|
(MODULES-11446) Add Amazon to display support in Puppet forge
|
|
|
|
(MODULES-11418) Resuable workflows for unit tests
|
|
This commit switches the GitHub Actions workflows for unit tests
over to using the reusable workflows in
puppetlabs/phoenix-github-actions.
|
|
(maint) Update PDK template
|
|
Modeling after the learnings of the support team in commit
puppetlabs/puppetlabs-puppet_metrics_collector@78dd858
This commit pins the github_changelog_generator gem to its latest
version to make it work, and the concurrent-ruby to an older version
to compensate for the version of PDK shipped in the dev-tools
container image.
|
|
In e4337c0, we updated the module according to PDK template 2.7.4,
which updated puppetlabs_spec_helper. The updated version of
puppetlabs_spec_helper removed the Beaker rake task, which we use
for acceptance testing.
This commit adds the voxpupuli-acceptance gem, which re-adds the
Beaker rake task.
|
|
The PDK Docker image does not contain any build tools, which causes
the installation of gems that use native extensions to fail.
This commit changes the Docker image used in the Auto Release
GitHub Action from the PDK image to the Puppet dev-tools image,
which contains packages like `make` necessary for building native
extensions.
|
|
This commit updates GitHub Actions to move away from both operating
systems and Actions that are nearing or past end-of-life.
|
|
This commit runs `pdk update` using the most recent template at the
time (2.7.4) and updates metadata.json to allow Puppet versions
< 9.0.0 in preparation for the release of Puppet 8.
|
|
Add maintenance notice
|
|
@joshcooper is this the appropriate support tier?
|
|
(MODULES-11283) curl for installing the latest nightly build
|
|
|
|
(maint) Add redirect to nightly puppet gem download
|
|
Update link to download latest nightly build of puppet gem
|
|
(maint) Add phoenix to CODEOWNERS
|
|
|
|
Dorin-Pleava/PUP-11370/github_actions_upgrade_windows
(maint) Github workflow now uses windows 2019
|
|
Upgraded github actions to use windows 2019 instead of windows 2016 as
it will be removed on March 15, 2022.
|
|
(maint) Pin async gem
|
|
Async 2.0.0 requires Ruby 3, so we're pinning to 1.x
|
|
Release prep v1.1.0
|
|
|
|
(MODULES-11197) Update to pdk-templates 2.2.0
|
|
Includes REFERENCE.md ToC fixes for MODULES-8183.
|
|
BobosilaVictor/MODULES-11167/11191/add-rocky-alma-modules
(MODULES-11167)(MODULES-11191) Add RockyLinux and AlmaLinux to mailalias_core metadata
|
|
mailalias_core metadata
|
|
(MODULES-10953) Update metadata.json and pdk version
|
|
To avoid having to update this everytime we release a new agent
platform, it should be enough to specify the supported OS, without
specific versions. It is assumed that for each OS in metadata.json, the
versions supported are the same as what the agent itself supports.
|
|
(MODULES-10945) Core module spring cleaning 2021
|
