Allow setting certificate path in pkl settings #301

New Issue

2025-12-30T01:23:19+01:00

adam commented

2025-12-30 01:23:19 +01:00

Originally created by @rohan-datar on GitHub (Apr 8, 2025).

I'm using pkl in an environment that uses custom certificates for communicating with a private repo with some pkl modules. For now, I've been copying the custom certificates from the system certificate store to ~/.pkl/cacerts but this is annoying because the certificates have relatively short expiration times. Would it be possible to add an option to the pkl:settings module that allows you to set a static certificate path that is not ~/.pkl/cacerts? I would like to do something like this:

amends "pkl:settings"

cacerts = "/etc/ssl/certs/"

Originally created by @rohan-datar on GitHub (Apr 8, 2025). I'm using pkl in an environment that uses custom certificates for communicating with a private repo with some pkl modules. For now, I've been copying the custom certificates from the system certificate store to `~/.pkl/cacerts` but this is annoying because the certificates have relatively short expiration times. Would it be possible to add an option to the `pkl:settings` module that allows you to set a static certificate path that is not `~/.pkl/cacerts`? I would like to do something like this: ```pkl amends "pkl:settings" cacerts = "/etc/ssl/certs/" ```

adam commented

2025-12-30 01:23:19 +01:00

@HT154 commented on GitHub (Apr 8, 2025):

I've not yet verified this works, but you might try symlinking ~/.pkl/cacerts to /etc/ssl/certs to avoid having to copy things around.

@HT154 commented on GitHub (Apr 8, 2025): I've not yet verified this works, but you might try symlinking `~/.pkl/cacerts` to `/etc/ssl/certs` to avoid having to copy things around.

adam commented

2025-12-30 01:23:19 +01:00

@rohan-datar commented on GitHub (Apr 8, 2025):

I've not yet verified this works, but you might try symlinking ~/.pkl/cacerts to /etc/ssl/certs to avoid having to copy things around.

Verified that this does work, but I don't think it's a great solution overall. I would still like the option of providing a custom cert path or telling pkl to use the system certs.

@rohan-datar commented on GitHub (Apr 8, 2025): > I've not yet verified this works, but you might try symlinking `~/.pkl/cacerts` to `/etc/ssl/certs` to avoid having to copy things around. Verified that this does work, but I don't think it's a great solution overall. I would still like the option of providing a custom cert path or telling pkl to use the system certs.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/pkl#301