Add cid to env when calling client-connect and client-disconnect script #133
Conversation
This file contains 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
|
@1848 sorry for the latency, but we don't really pay attention to GH as the development happens on the mailing list (that everybody pays attention too). Why isn't the common-name enough? |
|
Closing due to inactivity. Can be reopened should the OP have time/motivation to discuss it again. |
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.
Small patch to include the client id to the environment when calling client-connect or client-disconnect scripts.
Could be useful as "unique" client id.
I dont know if this is useful enough for a real PR, so this is more like an RFC currently.