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] 4 months ago
Published by github-actions[bot] 5 months ago
Published by github-actions[bot] 5 months ago
Published by github-actions[bot] 5 months ago
set -e
option when on windows (#3892) #3892 (YannC)terminationGracePeriod
#3909 (brian.mulier)Many plugins have been renamed for consistency and extensibility. We’ve implemented aliases for backward compatibility so that you don't need to update those names immediately. Everything will continue to work seamlessly, and you can take as much time as needed to rename those tasks and triggers.
Here are the key changes:
taskDefaults
are now pluginDefaults
to reflect the fact that you can set default values for all plugins, not just tasks.core
plugin rather than the file-system (fs
) plugin.io.kestra.core.models.triggers.types.Schedule
is now io.kestra.plugin.core.trigger.Schedule
. Again, this is a non-breaking change as we use aliases — don't worry when you see warnings in the UI. Those warnings are here to spread the message about renamed tasks and triggers, but you can take as much time as you need to rename them.CsvReader
→ CsvToIon
and CsvWriter
→ IonToCsv
.io.kestra.plugin.redis.TriggerList
is now io.kestra.plugin.redis.list.Trigger
.For more details about all these changes, check the Renamed Plugins Migration Guide.
The task runner classes are now shorter. For example, io.kestra.plugin.aws.runner.AwsBatchTaskRunner
is now io.kestra.plugin.aws.runner.Batch
. Check the task runner documentation for the full list of updated names.
Note that in contrast to the renaming mentioned in the previous section, we've renamed them directly (without using aliases) given it's a beta feature.
Kestra 0.17.0 uses a new mechanism to discover and load plugins. Plugins are now discovered and loaded using the standard Java Service Loader rather than Micronaut-specific Bean introspection. If you use custom plugins, follow the Migration Guide to make the necessary adjustments.
The wait
and transmitFailed
boolean properties of the Subflow
task are now set to true by default. This means that the default behavior of the Subflow
task is now waiting for the subflow execution to finish and transmitting the failed status to the parent flow's Subflow
task runs. If you want to keep the old default behavior, make sure to add the following to your pluginDefaults
:
pluginDefaults:
- type: io.kestra.core.tasks.flows.Subflow
values:
wait: false
transmitFailed: false
We previously serialized JSON objects with a NON_DEFAULT
strategy to save space (in the database) and optimize network bandwidth.
We changed that behavior so that all properties that are not null will now be included in the serialized JSON document. This fixes several limitations and lets us know when a default is purposely set. This also means that empty lists and maps are now serialized as empty objects (rather than not being serialized at all).
Published by github-actions[bot] 5 months ago
Published by github-actions[bot] 5 months ago
Published by github-actions[bot] 5 months ago
Published by github-actions[bot] 6 months ago
Published by github-actions[bot] 6 months ago
Published by github-actions[bot] 6 months ago
Published by github-actions[bot] 6 months ago
Published by github-actions[bot] 6 months ago
Published by github-actions[bot] 6 months ago
Published by github-actions[bot] 6 months ago
Published by github-actions[bot] 6 months ago
Published by github-actions[bot] 6 months ago
Published by github-actions[bot] 6 months ago
The only breaking change in this release is that we aligned all container labels. This means that if you filter any container resources by these labels, make sure to adjust them to match new labels.
Previous labels were:
New labels are:
GitHub issues that added these changes:
Published by github-actions[bot] 7 months ago
Published by github-actions[bot] 7 months ago