blackhat786000/Set Async GitHub Workflow Job Status

Set GitHub Actions workflow job status as success or failure based on Kafka event message

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
kafka_brokerBootstrap server URL with port <12.34.56.78:9092>yes
topic_nameTopic name that listener subscribes toyes
job_idAction input `job_id` should match message-value.job_id to determine job status from message-value.job_status. message-value={"job_id":"123","job_status":"SUCCESS"||"FAILED"}no
listener_timeoutTime in minutes for which listener will be actively waiting for target message10
authenticationAuthentication mechanism (e.g., SASL PLAIN)no
sasl_usernameSASL username for authenticationno
sasl_passwordSASL password for authenticationno
ssl_enabledEnable SSL connection (true/false)false
ca_pathPEM formatted file that contains a CA certificate to be used for validationno
client_certPEM formatted certificate chain file to be used for SSL client authenticationno
client_keyPEM formatted file that contains your private key to be used for SSL client authenticationno
group_idKafka consumer group IDno
group_prefixPrefix to be used to generate consumer group ID like <group_prefix><job_id>group-
success_whenConditional expression that evaluates to `true` to mark job status as SUCCESSno
fail_whenConditional expression to mark job status as FAILED. This option only has an effect if `success_when` is providedno
jinja_conditionalConditional jinja template that must return `SUCCESS` string or `FAILED` string to mark job status as SUCCESS/FAILEDno
namedescription
jsonJSON event message that marked job status as SUCCESS/FAILED