Description

Reduce the size of the Ansible job event messages generated by rhc-worker-playbook to avoid hitting data size limits at multiple junctions of the application.

Test Instructions

TBD - should entail running a playbook on a system and ensuring success.

Expected Results

Playbook run succeeds and this is captured in the UI as such.

Motivation / Justification

Currently playbook runs can generate an excessive amount of output, and

• succeed, but time out as a failure in the web UI because the cumulative output was too large to upload
• fail because the message size was too large for the IPC channels of RHC, but still time out the web UI because RHC has no communication method to inform the UI of the failure

Additional info

Potential solutions include filtering properties from the ansible runner job event messages to only the ones we need for Playbook Dispatcher. There is quite a great deal of output generated by ansible runner, and we use relatively little of it.

This list of properties is available internally / in the git repo, but they are not currently part of the public API spec.

Rather than assuming which properties we currently need and hardcoding that list into rhc-worker-playbook, it may be prudent to treat the properties as dynamic, and be given the list of props via API introspection or as part of an MQTT message, so it can be changed if we need it.