Local Test Deployment
It is possible to develop and test runners with sagas, queries and business rules locally without deploying to the cloud
Last updated
It is possible to develop and test runners with sagas, queries and business rules locally without deploying to the cloud
The fastest way to validate runner logic and end-to-end flows is to run a local, Spring-based event runner. You can then exercise your sagas and endpoints through the runner’s REST API. Follow the tasks below to get a local run working.
Update application.properties
Add/remove/adjust runner elements at the end of the file using the runner IDs and types you want to test (the default runner-admin_rpc-0001 and runner-admin_crud-0001 entries are core admin runners)
Change server.port if you want to avoid port conflicts
Update values.properties
Set rierino.system.mongodb.devops_main.uri to your MongoDB URI (example: mongodb://host:port). If you are not using MongoDB, contact Rierino for alternative configuration loading options.
Add any non-secret properties referenced as ${{...}} in your elements
Update secret.properties
Add any secret properties referenced as #{{...}} in your elements
Run the Gradle command in run.sh (make sure gradle is on your PATH)
Validate the runner is reachable
Health check example: http://localhost:1235/actuator/health
Test saga flow example: http://localhost:1235/api/rpc/Hello
Once it is running, you can call any endpoints exposed by the runners you enabled from your local test environment.
Last updated
