Repository navigation
Add tested Kestra batch screening and evidence example - #1
Merged
Merged
Conversation
Add a synthetic batch-screening flow and native fixture tests for Kestra 2.0.4. Run the engine in an unprivileged Docker container with no external network, real API keys or published ports. Keep the example marked as a candidate until all native tests pass.
Give the network-none fixture container a fixed hostname mapped to 127.0.0.1. Assert that resolution before starting Kestra and preserve the existing network and privilege limits.
Treat an absent Loop output collection as empty when every row has failed or been cancelled. Keep row errors in the exported review bundle and add bounded fixture diagnostics for unexpected native failures.
Link the Kestra example from the root README and document the verified 24-scenario native fixture run. Keep hosted sandbox execution distinct from the isolated test results.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a Kestra 2.0.4 example for submitting two fictional contacts as an asynchronous SanctionsKit batch, waiting for completion, and exporting retained evidence plus a CSV row summary. Failed and cancelled rows stay visible, and the workflow never approves onboarding. The root README now links the example and the integration README explains the tested setup.
The example uses a user-owned key for the free synthetic sandbox; production screening is paid. It bounds polling and HTTP retries, preserves the request key and body for retries, disables redirects, and validates row/evidence identity before exporting files.
Validation: the unchanged executable files at
3f9c56d940e80598c7dec22863637faeda1c10bapassed all 24 native scenarios on Kestra 2.0.4 with serdes 2.0.6 and Temurin 25 in CI run 37181224466. Five scenarios completed successfully and nineteen correctly rejected invalid/error conditions. The fixture used an isolated container with networking disabled and fictional local HTTP responses; no hosted API execution is claimed. All nine standalone language smoke checks passed at that commit. Final documentation links and whitespace checks pass locally; the PR checks verify the current head.This publishes a company-maintained example under its existing MIT license. It does not claim inclusion in the independent Kestra Blueprint catalog.