| Age | Commit message (Collapse) | Author |
|---|
|
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 sshkeys-core metadata
|
|
sshkeys-core metadata
|
|
|
|
|
|
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
|
|
Bump Ruby version in the static code analysis workflow to 2.6, as 2.5
will be EOL soon.
|
|
Update the workflow that tests with released Puppet gems to also test
with Puppet 7.
Remove testing with Puppet 5 from the workflows since it reached EOL.
|
|
Pin puppet-module-posix-system and puppet-module-win-system to an older
version since the newer ones do not bundle some gems that we use in
acceptance (i.e. beaker-module_install_helper), causing tests to fail.
|
|
Create a separate group in the Gemfile for pdk and puppet-blacksmith
which are only used for releasing. In the workflow, avoid installing the
release group.
|
|
Add beaker-puppet to unify core module gemfiles
|
|
luchihoratiu/maint-allow-git-to-use-long-paths-in-gh-actions
(maint) Allow git to use long paths in GitHub Actions
|
|
Due to unknown environment changes in GitHub Actions runners, we
encountered the following error:
`fatal: cannot create directory: Filename too long`
This commit allows git to use long paths in our GitHub Actions
workflows.
|
|
luchihoratiu/MODULES-10815-add-slack-notification-job
(MODULES-10815) Add Slack notification job
|
|
This commit adds a job to the `[Daily] Unit Tests with nightly Puppet
gem` workflow that notifies us the conclusion of it via Slack.
|
|
(MODULES-10832) Release prep for 2.2.0
|
|
|
|
|
|
(MODULES-10827) Exported sshkey already exists error
|
|
During the removal of `puppet-module-dev`, the pdk and puppet-blacksmith
gems were also removed by mistake. This commit makes us able to release
again.
|
|
Unit tests seem to be running much faster on Windows 2016 with GitHub
Actions than Windows 2019.
|
|
This commit adds the `commits` rake task and runs it in the Static Code
Analysis workflow as a step.
|
|
Using module https://github.com/ghoneycutt/puppet-module-ssh to export
and collect sshkey resources from nodes, an 'already declared' error
appears.
This happened because when the catalog is first converted to resouces,
the sshkey resource is added via
https://github.com/puppetlabs/puppet/blob/main/lib/puppet/resource/catalog.rb#L137,
where 'resource.ref'(https://github.com/puppetlabs/puppet/blob/main/lib/puppet/type.rb#L2548)
uses 'self.title'.
Since self.title goes to the title method defined in type.rb, it will
return a different title than the title method from
https://github.com/puppetlabs/puppetlabs-sshkeys_core/blob/main/lib/puppet/provider/sshkey/parsed.rb#L31.
This mismatch try to add both resource, resulting in the 'already
declared' error.
|
|
(MODULES-10800) Add GitHub Actions workflows
|
|
Added GitHub Actions workflows for `Static Code Analysis` and `Unit
Tests` that run each time there is a new `pull request` or `git push`.
`Unit tests` are also set to run every workday at `05:00:00 UTC`.
The `.yaml` config files of `Travis` and `AppVeyor` have been removed.
|
|
In preparation for the Puppet 7 release, the
`puppet-module-posix-dev-r2.7` and `puppet-module-posix-dev-r2.7` gems
had to be removed from `Gemfile` due to the following dependency error:
`puppet-module-posix-dev-r2.7` depends on
`puppet_litmus` which depends on
`bolt` which depends on
`puppet` which is locked to a version below 7
Also added the needed gems that were lost in the above removal process.
|
|
Dorin-Pleava/MODULES-10760/sshkeys_core_update_beaker_4
(MODULES-10760) Bump to beaker 4
|
|
|
|
(MODULES-10765) Implement public key certificate support
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(maint) Update Puppet VS Code Extension ID
|
|
(MODULES-10686) release preparation for 2.1.0
|
|
|
|
(maint) Update user type specs to match new behavior
|
|
`purge_ssh_keys` behavior will change with the next Puppet release
(6.16.0). This commit updates the tests to reflect the updated behavior.
See https://github.com/puppetlabs/puppet/pull/8157.
|
|
(PUP-10510) Fix sshkeys not being correctly purged
|
|
This commit updates the configuration file to point to the official Puppet VS Code Extension `puppet.puppet-vscode`
|
|
Dorin-Pleava/MODULES-10671/New_ssh_keys_types_open_ssh_8.2
(MODULES-10671) New SSH key types for OpenSSH 8.2
|
|
After adding support for composite namevars in version 2.0.0, the module
lost the ability to purge sshkeys. This happens due to Puppet being
unable to correctly match the names and types of the sshkeys to be
purged.
Part of the fix was done in
https://github.com/puppetlabs/puppet/pull/8174, which changes how a
resource is initialized if the provider implements a `title` method.
Additionally, we add the key name and type to be included in the output
shown by `puppet resource`.
|
|
Two new SSH key types were added on OpenSSH 8.2:
sk-ecdsa-sha2-nistp256@openssh.com(alias ecdsa-sk) and
sk-ssh-ed25519@openssh.com(alias ed25519-sk)
|
|
|
|
Release preparation for 2.0.0
|
|
|
|
(MODULES-7613) use name and type as composite namevar
|
