Environment secrets available in the hook stage

[amalucelli]

👋🏻 Hello, I'm trying to configure a custom scenario using the hooks (ACTIONS_RUNNER_HOOK_JOB_STARTED variable) on self-hosted runners, where I need an environment secret available in the stage where the hooks are executed. The workflow has the environment: foo set but I noticed this is not injected at that stage. Is this possible to configure?

[amalucelli]

I was reading the ADR related to the start/complete hooks, and it seems even some default environment variables should be exposed to those scripts:

The scripts will have access to the standard default environment variables

I think for the default variables it is working, as I can see them exposed if I inspect the process on the container created to run the hooks (cat /proc/{pid}/environ), but I don't see the custom variables there.

I'm using custom runners deployed by https://github.com/actions/actions-runner-controller if it gives any context on my installation.

I also found this PR that might be related: #1849, but I'm not sure if this should handle custom variables/secrets at that stage.