Make CI configuration easy to understand (and memorize) about pdk-templates HOT 5 CLOSED

@bittner I agree with you and speaking with the devs I think that's their ultimate plan but I think they are still clearing some barriers. In the meantime, I made some changes to the various CI configs to make them look more alike.

Also, I put up this PR, #88, to make validating one step instead of multiple steps.

from pdk-templates.

@bittner agree... this is the so-called puppet style: lot of files everywhere, spread on each and every possible location, with all the possible syntax flavors.
For instance: puppet uses the Puppetfile and PDK uses a YAML file (.fixtures.yml).
I rather prefer the Yaml version, but this is inconsistent, and it's another file to memorize.

from pdk-templates.

We do plan to do this. You can track the progress in https://tickets.puppetlabs.com/browse/PDK-709

from pdk-templates.

A recent blog post by @rnelson0 explains that the two PDK commands now seem to reliably do what is expected, and all the validation and test setup can be generated to work locally. Hence, we should be able to throw away all the complicated bundle, gem and rake command collections in all CI setups, once and forever.

Are there any plans to implement this before the end of this year? This should be easy and fast to do.

from pdk-templates.

This issue was moved to puppetlabs/pdk-planning#25

from pdk-templates.