Skip to content

Conversation

@Scirelgar
Copy link
Member

@Scirelgar Scirelgar commented Mar 6, 2025

Warning

There is still some clean up to do regarding unnecessary files that have been generated from the conversion, such as CHANGELOG and README.
Some testing would be required as well to make sure the addition of new GemFile, RakeFile and such doesn't interfere with the ones outside of the module.

Conversion

This integrates PDK by converting the site/profile module with pdk convert, following a given template.
Here's a list of files that are targeted by pdk convert.

Validation and testing

PDK compatible modules can be validated and tested with pdk validate and pdk test.

A workflow has been introduced to trigger both validation and testing followed by the creation of annotations that will show directly in the Files changed tab of future PRs.

Note

Currently, site/profile has not yet defined unit tests. Basic unit tests can be generated by pdk convert --add-tests, but most are failing. This will be the object of a future PR. For now, the workflow will simply declare that no tests were found and succeed anyway.

* updating ruby-version in Puppet validation action

* fixed two lines that were stopping the execution of `pdk validate`

* all files that are added or modified by `>pdk convert` at root

all files that are added by `>pdk convert` at root

files modified by `>pdk convert` at root

* Revert "all files that are added or modified by `>pdk convert` at root"

This reverts commit ce51ab3.

* all files that are added by `>pdk convert` at `site/profile/`

* adding basic workflow for puppet validation and unit testing, adding files/ to ignore field in `pdk/yaml`
* enhance PDK workflow with validation results annotation

* switch to inline command for run property in pdk_tests.yaml

* replacing shell script by python script to parse xml formatted result of `pdk validate`

* setting up pdk manually, rather than having to install python in container

* piping the output of `pdk validate` to pdk-validate annotation script

* using job environment variable to define directory targeted by scan
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant