Fix automation for task "Install PHP composer dependencies for background-jobs"
Motivation and Context
The goal here is to have the closest as possible to a fully automated role being applied, instead of dealing with timeouts and multiple executions of playbooks (which apply the role itself).
This patch's changes make use of parameters provided by the Ansible composer module instead of populating all options as extra arguments to the module inside the task we want to automate.
For more information, please read the official composer documentation and a thread on StackOverflow linked below.
Applied this role, against (fresh installed) Ubuntu machines using the particular versions affected by this change request;
Once we hit the failed step, it's also possible to verify with alternative methods, like running a playbook to apply this role starting from particular tasks like, e.g.: --start-at-task='Install PHP composer dependencies for background-jobs'
The timeout can be reproduced also inside the "testing virtual machine" (or jumping inside the container used y Molecule) by running the following:
Description
Fix automation for task "Install PHP composer dependencies for background-jobs"
Motivation and Context
The goal here is to have the closest as possible to a fully automated role being applied, instead of dealing with timeouts and multiple executions of playbooks (which apply the role itself).
This patch's changes make use of parameters provided by the Ansible composer module instead of populating all options as extra
arguments
to the module inside the task we want to automate.For more information, please read the official
composer
documentation and a thread on StackOverflow linked below.How Has This Been Tested?
Applied this role, against (fresh installed) Ubuntu machines using the particular versions affected by this change request;
--start-at-task='Install PHP composer dependencies for background-jobs'
The timeout can be reproduced also inside the "testing virtual machine" (or jumping inside the container used y Molecule) by running the following:
The root-cause for this timeout (see first screenshot) is triggered by the following:
Screenshots
BEFORE (broken)
AFTER (fixed)
Types of changes
Checklist: