We are pleased to announce a brand new release of Automatiko - 0.3.0
Automatiko supports building Kubernetes Operators as workflows that improves visibility into what operator does. It provides complete integration with Java Operator SDK that hooks into Kubernetes cluster and registers watchers and more. At the same time it allows to have access to Kubernetes API server via Fabric8 Kubernetes client. Workflows can perform operations on Kubernetes API server via Service Tasks that get Kubernetes client injected and receive events from Kubernetes via message events.
Automtiko provides support for building operators directly in the Kubernetes cluster with live reload without a need to rebuld the image and redeploy. Have a look at this blog post to see it in action.
Error handling has been improved to collect more information and present them in more accessible way.
Data objects can now be tagged as versioned
which will automatically track changes to them
and make a copy to any non null values. That will then build up a list of versions given variable had.
Versions are also avaiale to be easily accessed in the workflow definition which enables use cases
that requite comparing received data with already processed. Users can easily get access to
person$
previousVersion(person$)
variableVersion(person$)
Process management UI has been significantly improved to bring not only visibility but also operations support
Automatiko allows to tag variables (aka data objects) as auto-initialized
which will ensure that the
variable is initialized at the start of workflow instance. With this release there is alos support for simple types
false
0
empty string
Photographs by Unsplash.