I’m reviewing the remaining Environment Design TODOs, and I have a question about

[GLOBAL].ca_certs_path

. This is a BootstrapOption, which is inherently non-environment-sensitive. There’s clearly places where we need an environment-sensitive value, but we also need a value which is fixed to the environment where Pants is being run (e.g. in

scheduler.py

). Is the solution here to add a new option for process-level certs paths (which defaults to

ca_certs_path

), or something else?

so, i think that the theory in this case is that this might still be useful to provide via an environment, because it might be in a different location on Linux vs macOS for example

Well it’s more that you need to provide a value to construct the scheduler, which by definition is a bootstrap options

that’s my second point. i think that the ca_certs are only used for downloading artifacts… so I think that we can bootstrap without it? maybe not though.

it’s provided as an argument to the scheduler, and then for other uses a value from an environment would make sense

yea. @hundreds-father-404: so… more generally, i think that we should whack moles that we have identified along the path to particular use cases. so it would be good to spend some time mapping those out soon. while we can definitely identify potentially problematic options purely by inspection, we won’t really be able to prioritize them without those use cases in play

I think I’m getting a feel for what things make sense to migrate on a per-subsystem level, it’s really the blurring between bootstrap options and global options that’s getting me

yeah, ca_certs path is the trickiest one we have because of bootstrap options. If helpful, I could try taking that one

I think ca_certs just needs a design. I think having a second option for process-level certs would be a good start