Fix ssl_cert/ssl_key/ssl_ca examples to use file paths instead of file:// URIs

[Copilot]

The ssl_cert, ssl_key, and ssl_ca parameters in data/common.yaml were documented with file:// URIs, but these params expect plain filesystem paths written directly into .env. The *_source params are the correct ones for URI values.

Changes

• data/common.yaml: Replace file:///etc/... URI examples with plain paths for ssl_cert, ssl_key, ssl_ca in both the PuppetDB and Puppet Server integration sections

Before:

# pabawi::integrations::puppetdb::ssl_cert: 'file:///etc/puppetlabs/puppet/ssl/certs/agent.pem'
# pabawi::integrations::puppetdb::ssl_key: 'file:///etc/puppetlabs/puppet/ssl/private_keys/agent.pem'
# pabawi::integrations::puppetdb::ssl_ca:  'file:///etc/puppetlabs/puppet/ssl/certs/ca.pem'

After:

# pabawi::integrations::puppetdb::ssl_cert: '/etc/puppetlabs/puppet/ssl/certs/agent.pem'
# pabawi::integrations::puppetdb::ssl_key: '/etc/puppetlabs/puppet/ssl/private_keys/agent.pem'
# pabawi::integrations::puppetdb::ssl_ca:  '/etc/puppetlabs/puppet/ssl/certs/ca.pem'

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull request overview

This pull request corrects the documentation examples in data/common.yaml for SSL certificate configuration. The examples were incorrectly showing file:// URI notation for the ssl_cert, ssl_key, and ssl_ca parameters, when these parameters expect plain filesystem paths. The file:// URI format is only appropriate for the corresponding *_source parameters, which handle file copying/downloading operations.

Changes:

• Updated PuppetDB integration SSL parameter examples to use plain paths instead of file:// URIs
• Updated Puppet Server integration SSL parameter examples to use plain paths instead of file:// URIs

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.