Puppet Community

where I use store_fact and jinja to munge a bunch of data so I can use it

because the only way to actually make a variable in ansible is to write a module, or use jinja

Haha.. what are you doing with my Ansible repo?! I had almost the same :-D

Being a software dev that transitioned from Systems Engineering, I can say that trying to hide the code doesn't really help all that much, it just makes things complicated and then more "traditional" SysAdmins go back to no using Infra-as-code/Config Mgmt

my goal is to make interfaces for Jr folks that are intuitive and sane

and let devs/high level engineers write a little more code to make that happen

I want my entry level sysad to just know "if I set this hiera key to the right list of groups it works"

I'm running into an issue when using the lldpd module. Any thoughts or ideas on what might be happening (even if its me doing something stupid)?

<https://puppetcommunity.slack.com/archives/C0W298S9G/p1674069512717089>

Anyone else using Gitlab (and not Github) for their Puppet modules?

I'm going to open a puppet-lint PR to add an option to generate 'codeclimate' formatted json output.

If in your gitlab pipeline you save this to a file and add it as a codequality report, you get something similar to the work ewoud did for github.

ie this stuff <https://docs.gitlab.com/ee/ci/testing/code_quality.html#view-code-quality-results>

I would also benefit from this :slightly_smiling_face:

<@U01TK2XG0S0> this may be interesting for customers who are using/moving to gitlab

Cool.  Good to know there's a few people interested.

This is what I've come up with so far. <https://github.com/puppetlabs/puppet-lint/pull/78/files>

Working much like the `--sarif` option.  Not sure I like it that way though.  Maybe it wants to be more like the GitHub solution and use an environment variable such that it could work with the Rake task??

It probably be better if the existing gitlab jobs the PDK template ships with didn't need messing around with too much.

I don't know about the PDK - in GHA it does weird things and the annotations aren't enabled with PDK

that said, we also aren't using it in Vox Pupuli since we're still on version &lt; 3 I think

but with GHA it can parse output on stdout so you can use env vars; no idea about GitLab CI

ewoud: I need the output to end up in a file and for it not to contain other output (eg. from other rake tasks).

I guess with github it was easier because the output could be freely mixed in with anything else on stdout?

Maybe I default to writing a file if `GITLAB_CI` is `true` but also provide a way of turning this off (maybe reusing env var ``CODE_QUALITY_DISABLED`` <https://docs.gitlab.com/ee/ci/testing/code_quality.html#disable-code-quality> )
That's used for pipelines that use this template. <https://docs.gitlab.com/ee/ci/testing/code_quality.html#disable-code-quality>