Repository navigation
Remove cron schedules and settle names before the first release - #4
Merged
Merged
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.
Nothing uses this module yet, so this removes what was only kept for continuity while the cost of changing it is still zero. Cron schedules are gone, along with the RunFlow error that existed for them. Connecting and log export now read only
TEMPORAL_ADDRESS,TEMPORAL_NAMESPACEand OpenTelemetry's standard OTLP variables. A malformed log endpoint is rejected at startup, because the exporter would otherwise accept it and lose every record, and a trailing slash on the general endpoint now works as the OpenTelemetry spec describes.FlowConfigandStepConfigJSON keys now match their field names:fair_key,max_attempts,max_interval,no_retry,attempt_timeoutandpickup_timeout.