Is there any way of using the rugged git shipped with PE with an external Git provider that requires mutual TLS over HTTPS (no ssh).
s
steveax
09/22/2026, 9:43 PM
Looks like rugged doesn't have support for mTLS.
a
Argon Wade
09/23/2026, 1:02 AM
I got a forward proxy setup through an F5, and that got us past the mTLS hurdle. I haven't figured out the git part yet. Passing a gitlab personal access token in the header via a curl command for testing is easy enough and confirms the forward proxy, but I just haven't figured out how to get PE to do the same via rugged and PE class params.
Argon Wade
09/23/2026, 1:03 AM
Plan to work on it some more tomorrow, but will likely just downgrade to shellgit since we lose our on-premise gitlab on Friday.
Argon Wade
09/24/2026, 10:37 AM
Ok, I managed to successfully connect and build an environment if the Puppetfile is empty. Everything inside the control repo is present, so it does work.
From what I can tell however, PE handles modules inside the Puppetfile differently. What class/parameter combo is needed for that portion?