From ce5471fc9f0d2709ba4019df0ed586232dc85ce7 Mon Sep 17 00:00:00 2001 From: Player256 <92082372+Player256@users.noreply.github.com> Date: Thu, 23 Feb 2023 20:51:39 +0530 Subject: [PATCH] Update collection_integration_updating.rst (#80037) --- .../collection_integration_updating.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docsite/rst/community/collection_contributors/collection_integration_updating.rst b/docs/docsite/rst/community/collection_contributors/collection_integration_updating.rst index 46d18c06ef0..b519c4d4d1b 100644 --- a/docs/docsite/rst/community/collection_contributors/collection_integration_updating.rst +++ b/docs/docsite/rst/community/collection_contributors/collection_integration_updating.rst @@ -106,7 +106,7 @@ We will add the following code to the file. .. code-block:: yaml # https://github.com/ansible-collections/community.postgresql/issues/NUM - # We should also run the same tasks with check_mode: yes. We omit it here for simplicity. + # We should also run the same tasks with check_mode: true. We omit it here for simplicity. - name: Test for new_option, create new user WITHOUT the attribute community.postgresql.postgresql_user: name: test_user @@ -149,7 +149,7 @@ We will add the following code to the file. Then we :ref:`run the tests` with ``postgresql_user`` passed as a test target. -In reality, we would alternate the tasks above with the same tasks run with the ``check_mode: yes`` option to be sure our option works as expected in check-mode as well. See :ref:`Recommendations on coverage` for details. +In reality, we would alternate the tasks above with the same tasks run with the ``check_mode: true`` option to be sure our option works as expected in check-mode as well. See :ref:`Recommendations on coverage` for details. If we expect a task to fail, we use the ``ignore_errors: true`` option and check that the task actually failed and returned the message we expect: