Last week we worked hard into moving forward our services and making sure that they can be deployed into an AWS Kubernetes Cluster and also a GCE Kubernetes Cluster. This will enable us to validate our examples and blueprints in a more consistent way release after release.
We are looking into plugging in our Acceptance Tests in our pipelines to start covering more complex scenarios.
@MiguelRuizDev worked on improving the Task Service Incubator project and added a UI using Angular 6.
@igdianov defined the next steps for the graphql integration and modules dependencies to make it more generic.
@daisuke-yoshimoto working on the Cloud BPMN signal mechanisms examples and acceptance tests.
@constantin-ciobotaru worked for organization controllers
@lucianoprea used the Activiti Cloud Infrastructure inside a template project along with the logging and tracing
@ryandawsonuk Made it possible to run the apps service is Kubernetes by putting it on a new example app – in the docker-compose example its embedded in the registry but both register on the gateway with the same route so that the external API is the same. Switched Activiti keycloak integration module to using autoconfiguration. Reviewed and merged changes from @igdianov to make graphql notifications with websockets available through the gateway.
@erdemedeiros made sure that the runtime bundle relies on the new Java API: covered part of the process instance and process definition REST APIs.
@salaboy worked on getting the new Spring Cloud Gateway up and running with the Spring Cloud Kubernetes Discovery Client for dynamic routes discovery.
This week we look forward to migrate our quickstart to follow our new BluePrint structure and also Daisuke (@daisuke-yoshimoto) and myself (@salaboy) will be presenting at JJUG CCC Spring 2018 Conference in Tokyo, Japan. If you are around Tokyo, feel free to drop me a message via Twitter and we can catch up while I’m around.
Get in touch if you want to contribute: https://gitter.im/Activiti/Activiti7
We are looking forward to mentor people on the technologies that we are using to submit their first Pull Request 😉