What's the reasoning behind run-once[task]?

[bendem]

I understand that the rule prevents "bad things" from happening when using strategy: free, but it's not explained anywhere what kind of "bad things". The ansible-lint rule doc refers the user to the ansible documentation which has no mention of problems combining bother together.

The doc also says it's ok to use noqa if we assessed the problem, but it again doesn't tell what the problem could be.

https://ansible-lint.readthedocs.io/rules/run-once/

This comment seems to imply that the rule exists because run_once is really a best effort when combined with free, but it's not actually mentionned in the doc (ansible or ansible-lint).
#2815 (comment)

[bluikko]

I thought that free with run_once just doesn't work and run_once is ignored. I might be wrong.

Personally I have turned this rule off - as long as it cannot detect the strategy used it just contributes to proliferation of noqas.

[ssbarnea]

It is your decision. The reason for its existence is that people made use of run_once extensively even for tasks that could produce disasters when run twice. The rule is there to remind people that si more of a "try-to-run-only-once" attempt. What really happens depends on the context.

[bluikko]

I checked the links contained in the OP link and didn't notice explanations about run_once + free, as the OP stated. Maybe you can confirm what happened in such a case?

[bendem]

Proposed change: #3187