feat: add GLEAM_CACERTS_PATH env variable

[winstxnhdw]

Revival of #3459

Tagging @lpil as he was the previous reviewer.

Closes #3246

[lpil]

Thank you!

It looks like these would be used for all HTTP requests rather than just for the Hex API. Is that what we want or would that be too restrictive if we wanted to make requests to other domains too?

How might we test this change?

[winstxnhdw]

It looks like these would be used for all HTTP requests rather than just for the Hex API. Is that what we want or would that be too restrictive if we wanted to make requests to other domains too?

Again, it seems standard to have the certificates apply to all HTTP requests. In fact, a partial application would be surprising and frustrating behaviour.

[winstxnhdw]

Hey, any updates?

[lpil]

I just tested this and node does not silently discard the error, it emits an ugly looking warning.

Make it return an error if an error occurs, thank you.

[winstxnhdw]

I just tested this and node does not silently discard the error, it emits an ugly looking warning.

Make it return an error if an error occurs, thank you.

I am not sure what you mean. I am returning an error. Can you describe how you reproduced that warning? I am not getting an issue on my end.

[lpil]

I set the variable and then ran npm install.

We will be returning an error for invalid certs.

[winstxnhdw]

Any ideas how I can propagate the error out of get_or_init?

[lpil]

You would need to not use get_or_init, or to handle the error at each place it is used.