Infinitely scalable, event-driven, language-agnostic orchestration and scheduling platform to manage millions of workflows declaratively in code.
APACHE-2.0 License
Bot releases are visible (Hide)
Published by github-actions[bot] 7 months ago
Published by github-actions[bot] 7 months ago
Published by github-actions[bot] 7 months ago
Published by github-actions[bot] 7 months ago
Published by github-actions[bot] 7 months ago
Published by github-actions[bot] 8 months ago
Published by github-actions[bot] 8 months ago
Published by github-actions[bot] 8 months ago
Published by github-actions[bot] 8 months ago
Published by github-actions[bot] 8 months ago
tasks
and errors
property of Pause task (#3122) #3122 (YannC)ExecutionQueued
. To efficiently drain all your executions, you can stop the Webserver and the Scheduler, and then wait for the Executor and the Worker to finish pending executions. Once all executions are finished, you can upgrade to 0.15.0.backfill
source code property in the Schedule
trigger in favor of the new UI backfill feature. You can still have backfills specified in the source code but they will have no effect, as backfill is now an API-first feature.id
instead of name
: the name
property is deprecated in favor of id
for consistency with the rest of the Kestra flow configuration, including the flows, tasks, and triggers. This deprecation is implemented in a non-breaking way so that you don't need to immediately change your existing flows in order to successfully migrate to 0.15.0, but we recommend using the id
property at least for new flows. The name
property will be removed in the future.outputs
property of a Subflow
task is deprecated. Instead, use flow outputs
to pass data between flows. If you have many subflows passing data between each other and you need more time for the migration, you can add a configuration to keep the old behavior. Check the migration documentation for more details.scheduleConditions
deprecation: to make the configuration more consistent, we've unified the scheduleConditions
with the generic trigger conditions
. As a result of this change, the scheduleConditions
property is marked as deprecated; simply rename it to conditions
to future-proof your flows. This change is implemented in a non-breaking way, so you don't need to immediately change your existing flows in order to successfully migrate to 0.15.0. However, we recommend using the conditions
property at least for new flows. The scheduleConditions
property will be removed in the future. For more details and examples, check the Schedule Conditions migration guide.Published by github-actions[bot] 9 months ago
Published by github-actions[bot] 9 months ago
Published by github-actions[bot] 9 months ago
kestra.variables.recursive-rendering
as a settings + introduce render() function (#2834) #2834 (brian-mulier-p)tasks
flow property #2769 (brian.mulier)of
#2756 (brian.mulier).kestraignore
handling to its own KestraIgnore class #2792 (brian.mulier)Published by github-actions[bot] 9 months ago
Published by github-actions[bot] 10 months ago
Published by github-actions[bot] 10 months ago
Published by github-actions[bot] 10 months ago
Published by github-actions[bot] 10 months ago