From ad369031a97d23936ad04fc7b15cfefd849a383e Mon Sep 17 00:00:00 2001 From: Alex Schultz Date: Tue, 15 Sep 2020 10:38:31 -0600 Subject: [PATCH] Add no_log to os_user async status When verbosity is turned up, the result of the os_user async may contain sensitive information so we should leverage the sensitive log variable for it. Change-Id: I4f21b281e7c7328dd57210dab5ba6785a6c6ddd8 (cherry picked from commit 3dd0e7b8a1cf68af84fc947cd60b8f4ae7133640) --- .../roles/tripleo_keystone_resources/tasks/users.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tripleo_ansible/roles/tripleo_keystone_resources/tasks/users.yml b/tripleo_ansible/roles/tripleo_keystone_resources/tasks/users.yml index b507ec13e..dc34d4823 100644 --- a/tripleo_ansible/roles/tripleo_keystone_resources/tasks/users.yml +++ b/tripleo_ansible/roles/tripleo_keystone_resources/tasks/users.yml @@ -34,6 +34,8 @@ loop_var: tripleo_keystone_resources_data - name: "Check Keystone user status" + # needed because the results may have the full information when verbosity is turned up + no_log: "{{ tripleo_keystone_resources_hide_sensitive_logs | bool }}" async_status: jid: "{{ tripleo_keystone_resources_user_async_result_item.ansible_job_id }}" loop: "{{ tripleo_keystone_resources_user_results.results }}"