Repository navigation
Fix workflow cron API compatibility for CLI 0.7.3 - #87
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.
Workflow creation and updates fail with HTTP 422 after Platform moved scheduling into
schedule; human list/detail output also expects removed top-level fields. This updates the CLI to the current API and prepares patch release 0.7.3.--interval-secondswith--schedule-cronfor five-field UTC expressions or six fields with seconds. Cron validation stays in the API.schedule: null, preserving the CLI default.--schedule-cron nullremoves a schedule on update; omission preserves it.--schedule-enabled true|falseand serialize it asschedule.enabled. Preserve existing cron/pause state when only the other field changes, and reject contradictory manual/pause flags before HTTP.Examples
Creation sends:
{ "name": "alerts", "query": {"database": "analytics", "sql": "SELECT 1"}, "schedule": {"cron": "*/5 * * * *", "enabled": false}, "sinks": [] }Resume sends
{"schedule":{"enabled":true}}; removing the schedule sends{"schedule":null}. No top-levelenabledorinterval_secondsis sent. The old interval flag is rejected rather than approximated as a cron schedule.Validation
1ea477awith zero findings, including code quality.1ea477a: CLI tests and CLI against Platform Docker Compose.dist plan --tag v0.7.3pass.Durationimport warning insrc/commands/insert.rsis unchanged.v0.7.2was tagged separately from merged main. This PR does not publishv0.7.3.