I have asked this a few months ago in the BigFix slack but I didn’t get any answer.
We are trying to find a way to let a multiple-action to continue its execution even when downloads have failed.
Our specific case scenario is related to the Chrome Fixlets:
Our SAs team test a baseline with the latest updates in a non-prod environment, once it is tested and validated, the baselines is officially approved to be deployed in production environments(No changes/updates are allowed to the baseline as that would break/violate the QA process).
So often, Google will release updates for Chrome and remove the downloads for the old version of the software hence BigFix is not longer able to download the content from Google.
This has happened right after we deploy the actions containing the previous version of the browser, and during the time it is deployed there is a new version. The action will stay in a
Pending Downloads status and won’t move from there.
Is there any way to allow the download to be marked as Failed and let the servers execute the rest of the sub-actions?
At that point we would prefer to miss that single update than miss all the security updates.
I have found multiple similar questions. None of them seem to work:
I’m also aware of the possibility to use an action that installs the latest available version but that would require that we ignore the validation of the sha hashes which could mean a potential security risk.
How to allow a multiple-action to fail a download after an specific amount of retries and let the rest of sub-actions to run.