From 78c9fb415954ca630f028fe7a7d154658fc41422 Mon Sep 17 00:00:00 2001 From: Niranjan Meghwal <56632168+NiranjanMeghwal@users.noreply.github.com> Date: Tue, 4 Oct 2022 02:19:43 +0530 Subject: [PATCH] replace with boolean true/false (#78950) --- docs/docsite/rst/reference_appendices/YAMLSyntax.rst | 4 ++-- docs/docsite/rst/reference_appendices/faq.rst | 4 ++-- docs/docsite/rst/reference_appendices/general_precedence.rst | 2 +- docs/docsite/rst/reference_appendices/test_strategies.rst | 4 ++-- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/docsite/rst/reference_appendices/YAMLSyntax.rst b/docs/docsite/rst/reference_appendices/YAMLSyntax.rst index d72d31628ce..f80e57c5619 100644 --- a/docs/docsite/rst/reference_appendices/YAMLSyntax.rst +++ b/docs/docsite/rst/reference_appendices/YAMLSyntax.rst @@ -74,8 +74,8 @@ These are called "Flow collections". Ansible doesn't really use these too much, but you can also specify a :ref:`boolean value ` (true/false) in several forms:: - create_key: yes - needs_agent: no + create_key: true + needs_agent: false knows_oop: True likes_emacs: TRUE uses_cvs: false diff --git a/docs/docsite/rst/reference_appendices/faq.rst b/docs/docsite/rst/reference_appendices/faq.rst index feeb99bdac4..611fb0ba1f8 100644 --- a/docs/docsite/rst/reference_appendices/faq.rst +++ b/docs/docsite/rst/reference_appendices/faq.rst @@ -795,14 +795,14 @@ and backups, which most file based modules also support: - name: run validation, this will change a lot as needed. We assume it returns an error when not passing, use `failed_when` if otherwise. shell: run_validation_commmand - become: yes + become: true become_user: requiredbyapp environment: WEIRD_REQUIREMENT: 1 rescue: - name: restore backup file to original, in the hope the previous configuration was working. copy: - remote_src: yes + remote_src: true dest: /x/y/z src: "{{ updated['backup_file'] }}" always: diff --git a/docs/docsite/rst/reference_appendices/general_precedence.rst b/docs/docsite/rst/reference_appendices/general_precedence.rst index 3fbc98b2b7b..cf347ea903c 100644 --- a/docs/docsite/rst/reference_appendices/general_precedence.rst +++ b/docs/docsite/rst/reference_appendices/general_precedence.rst @@ -101,7 +101,7 @@ When set in a playbook, variables follow the same inheritance rules as playbook - hosts: cloud gather_facts: false - become: yes + become: true vars: ansible_become_user: admin tasks: diff --git a/docs/docsite/rst/reference_appendices/test_strategies.rst b/docs/docsite/rst/reference_appendices/test_strategies.rst index 9577bcd2e38..09a3d73c05e 100644 --- a/docs/docsite/rst/reference_appendices/test_strategies.rst +++ b/docs/docsite/rst/reference_appendices/test_strategies.rst @@ -31,7 +31,7 @@ things in your playbooks. - ansible.builtin.service: name: foo state: started - enabled: yes + enabled: true If you think the service may not be started, the best thing to do is request it to be started. If the service fails to start, Ansible will yell appropriately. (This should not be confused with whether the service is doing something functional, which we'll show more about how to @@ -55,7 +55,7 @@ want certain steps to execute in normal mode even when the ``--check`` flag is u tasks: - ansible.builtin.script: verify.sh - check_mode: no + check_mode: false Modules That Are Useful for Testing ```````````````````````````````````