You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On PE 2019, PE 2021 and probably PE2023 we get the following warning when code-manager is active but no r10k private key is set:
2024-07-28T13:54:42.124Z WARN [async-dispatch-2] [p.c.config] No default private key provided. Code Manager will not be able to access most git repositories over ssh. Please set 'puppetlabs.code-manager.git.private-key'
2024-07-28T13:54:42.125Z WARN [async-dispatch-2] [p.c.config] No default private key provided. Code Manager will not be able to access most git repositories over ssh. Please set 'puppetlabs.code-manager.git.private-key'
This is a bit misleading when you've only http(s) control repositories configured. In that case the private key isn't required at all. The warning is problematic because multiple customers analyse their logfiles and they match on ERR and WARN.
Expected Behavior
Above log message should only happend when:
code manager is enabled
a repository is configured that's used via ssh
no private key is is configured
As an alternative, only support ssh access when a private key is set.
Describe the Bug
On PE 2019, PE 2021 and probably PE2023 we get the following warning when code-manager is active but no r10k private key is set:
This is a bit misleading when you've only http(s) control repositories configured. In that case the private key isn't required at all. The warning is problematic because multiple customers analyse their logfiles and they match on
ERR
andWARN
.Expected Behavior
Above log message should only happend when:
As an alternative, only support ssh access when a private key is set.
Steps to Reproduce
set
run puppet agent -t
restart pe-puppetserver
Environment
Additional Context
I would have submitted a patch but the PE license prohibits sharing patches, the repo is private and #10 isn't resolved yet.
The text was updated successfully, but these errors were encountered: