Set SDK_SYSTEMD_SECRET_SOCKET during hook invocation - #997
Open
tlm wants to merge 2 commits into
Open
Conversation
Expose the systemd secret socket path to SDK hooks via the SDK_SYSTEMD_SECRET_SOCKET environment variable so that SDK authors are not required to hard-code the socket location and can adapt if it changes over time.
jonathan-conder
approved these changes
Aug 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds
SDK_SYSTEMD_SECRET_SOCKETto the environment for all SDK hookinvocations, set to the path of the workshop systemd secret socket.
This allows SDK authors to read the socket location from the environment
rather than hard-coding it, so that the path can change over time
without breaking existing SDKs.
Self-review quick check
Docs