ljkimmel

That's a good workaround that I was not aware of. This does help me in one scenario that I have. However, consider the following scenario: I use the archive type...

Is this still on the roadmap? Is there an approximate ETA?

> I think we would like to handle this via the right tags. I would like to tag the repo with the correct STIG release versions and have the right...

Why are we still referring to the v1rX STIG? We are talking about Red Hat Enterprise Linux, yes? Version 2 of the STIG has been available since mid 2018 and...

It appears that V-71961 was updated back on Nov. 8, 2019 to accept only one user as input. At the time attributes were still in use and the attribute was...

While this is probably a good thing to have configured in general I don't think we want to be validating things that aren't mandated in the STIG.

Sure. For example your `jenkins_epel_url`, `jenkins_rpm_repo_key` and `jenkins_rpm_repo_url` are all statically defined in var/{{ansible_distribution}}.yml but you don't allow for them to be overrridden. Perhaps define them in {{ansible_distribution}}.yml with the...

Also, I get the idea that Jenkins, by default, expects to be connected to the internet for plugin installation. I'm not sure the details of how to do it but...