Add 'origin' field to launch events #872
Merged
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
Lets us differentiate launches from different BinderHub installations
|
/cc @betatim |
|
Looks good. Do you think we need some normalising capabilities or will need them? For example the OVH cluster can be reached via multiple hostnames, should we let the operator of the hub configure how to normalise those (into one hostname?)? I'm tending towards "no". |
|
@betatim hmm, that's a good point actually. I think it might be a good idea to allow that - especially if we want to not expose the hostnames to end users. That'll futz with |
|
@betatim updated |
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.
Lets us differentiate launches from different BinderHub
installations