Skip to content

ICSHWI-9040: Remove status from deployment/command, keep track of whether the...

Zoltan Runyo requested to merge ICSHWI-9040-awx-webhook-and-status-update into develop

ICSHWI-9040: Remove status from deployment/command, keep track of whether the webhook has fired or not for each job

Backend modification based on ICSHWI-9003 comments.

Remove status from deployment/command.

  • We will fetch the job to know the status,
  • There is no need for strange update side effects.

Send awx job output (logs) only when asked for.

  • It is big and we often don't need it.
  • Provide an option in the query to return logs OR create a separate endpoint for the job logs.

Keep track of whether the webhook has fired or not for each job

  • If the webhook has fired, we don't need to issue a query AWX for updates, just return what is in our database
  • If the webhook has not fired, issue a direct query to AWX when we query the deployment/command/job
  • This way we will never get stuck with stale data.
  • Throw a big error if the webhook does not fire in the time frame we expect The webhook going down is a big deal and we need an alert Send an email? Prometheus exporter? Make new API endpoint which can report internal errors? Detecting an error should be pretty easy: We expect a webhook update from AWX almost immediately after starting the job If detect that the job has finished (success, failure) via direct query but have not gotten any webhook update, that is a bad sign.

Merge request reports