- Mar 31, 2022
-
-
Christophe Chaudier authored
-
- Jan 24, 2022
-
-
- Nov 09, 2021
-
-
- Oct 26, 2021
-
-
- Oct 19, 2021
-
-
- Oct 13, 2021
-
-
- fix: [201] Trailing whitespace REMOVED - fix: meta-no-tags: Use 'galaxy_tags' rather than 'categories' REPLACED + role in Debian 10 only - fix: [601] Don't compare to literal True/False FIXED
-
- Oct 12, 2021
-
-
Ansible-lint: ``` Include has some unintuitive behaviours depending on if it is running in a static or dynamic in play or in playbook context, in an effort to clarify behaviours we are moving to a new set modules (ansible.builtin.include_tasks, ansible.builtin.include_role, ansible.builtin.import_playbook, ansible.builtin.import_tasks) that have well established and clear behaviours. This module will still be supported for some time but we are looking at deprecating it in the near future. ``` Fix: I have decided to go for ansible include_tasks module because it is more versatile and on a par with this module (for more info about differences between new modules, see [here](https://docs.ansible.com/ansible/latest/collections/ansible/builtin/include_module.html)
-
Shell module is not needed here. According to various sources (https://www.youtube.com/watch?v=57gAqKvAKck or https://stackoverflow.com/questions/56663332/difference-between-shell-and-command-in-ansible) it is not useful to use shell ansible module when not working with operands. Therefore I have decided to switch every actions to command module, more secure. Ansible-lint says "Shell should only be used when piping, redirecting or chaining commands"
-
refactor: changed variables pattern to be more consistent with ansible good practises and more flexible to use. refactor: remove useless comment doc: Readme in English and French
-
- Oct 08, 2021
-
-
This feature is system-related, not yunohost-related
-
- May 01, 2021
- Mar 10, 2021
-
-
Romain Thouvenin authored
-
- Nov 16, 2020
-
-
Romain Thouvenin authored
-
- Sep 17, 2017
-
-
sylvainar authored
-
- Aug 24, 2017
- Aug 23, 2017