feature: Early or lazy channel creation configuration option#115
Open
feature: Early or lazy channel creation configuration option#115
Conversation
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
Provided a boolean configuration option in the yaml file named
create_channel_early. When true (default), after calling the/createendpoint a Channel GenStateMachine process is inmediatelly created and started in waiting state.When this option is
false, the Channel GenStateMachine process is created only when there is a websocket or sse connection.Adjusted a timer to control how often a token life remaining validation ocurs.
Bump version of some dependencies.
Category
Checklist