Repository navigation
Replies: 2 comments 6 replies
|
Hello there. So, it's at the level of the task that one has to manage the idempotency for the playbook. (using There are several ways to implement that for you and maybe the community:
|
|
Hi,
My idea was to allow the user to provide the command.
My reasoning was because it is such a common case for occ commands to provide an optional easier way instead of having to always write two tasks. A bit like the create and remove keywords for shell. But I'm not hung up on this idea.
Whoa! Nice idea, I was not aware of this way to get app info.
|
Uh oh!
There was an error while loading. Please reload this page.
Trying to keep the ticket #416 a bit clean by continuing in a discussion...
I know ! Part of why I was looking for a galaxy role was me giving up on ldap conf via occ. My idea was to have "test_command" that i would need to provide on each occ run. I attach my file occ.yml. Maybe it can provide some ideas. Sorry it's in txt format github does not like yml files...
occ.txt
I would install apps like this
So what we could do as a first step is to allow run_occ to receive a cmd to decide if a change is needed.
When no test cmd / function is provided the behavior could stay the same.
All reactions