#Still interested on some ideas regarding
1 messages · Page 1 of 1 (latest)
Hmm no, it is actually a surprising behavior (and root of a bug on our end after): the execState's SSH_AUTH_SOCK env var is the value of the os.getenv("SSH_AUTH_SOCK"), which I only do once in the client when initializing the clientMetadata (not processed yet)
I don't know how this ends up being stored in this execState. As I right away process it and stored the processed value in the contextmetadata
What I'd like, as we expand home, is to retrieve the actual value of the metadata.SSHAuthSockPath
it's in filteredEnvs
hm, no technically it should work
but you do actually want state.spec.Process.Env I think
also, can you check that the processed value is actually getting set in clientMetadata
also, wait, that value shouldn't be ending up in the executor spec at all
it should be the value mounted by MountSocket
How do you know ?