On Friday 18 June 2021 at 23:10:46, jane p wrote:
> Would you mind addressing the scenarios and implementation options of
> installing/updating the system?
If you install, you want ansible to make changes (obviously, I think)
If you install a second time (with the same playbook) you want no further
changes to be made, because what needed to be installed has already been
instealled.
If you update, you want the system to be updated (again, pretty obvious).
If you update a second time (with the same playbook) you want no further
changes to be made, because the system has already been updated, nothing
further needs updating; the system should be left as it is.
> I think there is a conflict between the virtue of avoiding state
> changes on consecutive runs, and simplicity in implementation.
What do you think that conflict is?
What you would like to see, or what example can you give, as a "simple
implementation" which does not leave the target system in the same state after
every run?
Antony.
--
"Have you been drinking brake fluid again? I think you're addicted to the
stuff."
"No, no, it's alright - I can stop any time I want to."
Please reply to the list;
please *don't* CC me.
