dns_resolver_conf

History

Bertrand Lanson 6218ed1fdd All checks were successful test / Linting (push) Successful in 28s Details test / Molecule tests (default, ubuntu2004) (push) Successful in 47s Details test / Molecule tests (default, debian12) (push) Successful in 1m15s Details test / Molecule tests (default, debian11) (push) Successful in 1m24s Details test / Molecule tests (default, ubuntu2204) (push) Successful in 52s Details test / Molecule tests (with_custom_config, debian11) (push) Successful in 56s Details test / Molecule tests (with_custom_config, ubuntu2004) (push) Successful in 31s Details test / Molecule tests (with_custom_config, debian12) (push) Successful in 1m0s Details test / Molecule tests (with_custom_config, ubuntu2204) (push) Successful in 46s Details feat: add become: true, add vagrant tests, add systemd-resolved service check to avoid failure if service is not on host		2023-12-01 18:36:27 +01:00
..
group_vars	feat: add become: true, add vagrant tests, add systemd-resolved service check to avoid failure if service is not on host	2023-12-01 18:36:27 +01:00
converge.yml	feat: add become: true, add vagrant tests, add systemd-resolved service check to avoid failure if service is not on host	2023-12-01 18:36:27 +01:00
molecule.yml	feat: add become: true, add vagrant tests, add systemd-resolved service check to avoid failure if service is not on host	2023-12-01 18:36:27 +01:00
requirements.yml	feat: add become: true, add vagrant tests, add systemd-resolved service check to avoid failure if service is not on host	2023-12-01 18:36:27 +01:00
verify.yml	feat: add become: true, add vagrant tests, add systemd-resolved service check to avoid failure if service is not on host	2023-12-01 18:36:27 +01:00