cli socket path env

[kfox1111]

When setting up a more traditional system layout, where your systems socket is under (/var)/run, it would be nice to be able to override the default socket lookup path with an environment variable in spire-agent api and spire-server entry type commands.

[rturner3]

This sounds reasonable @kfox1111. We would welcome a PR with those changes.

[kfox1111]

SPIFFE_ENDPOINT_SOCKET for the spiffe workloadload socket for spire-agent seems like the thing to do.

for the server api, its less clear.

SPIRE_SERVER_ADMIN_SOCKET?

[rturner3]

SPIRE_SERVER_ADMIN_SOCKET?

SGTM

[kfox1111]

After some discussion, we may want to do this in 2 phases. I would think client changes can be made safely without much of a heads up to behavioral changes? While run is a more disruptive change that may need a minor version bump at least as a heads up?

1. Patch change
   • spire-agent client changes
   • spire-server client changes
2. Minor change
   • spire-agent run change
   • spire-server run change