-
Bug
-
Resolution: Won't Do
-
Minor
-
None
-
DO417 - RHAAP2.4-en-1-20240627
-
None
-
False
-
-
False
-
en-US (English)
Please fill in the following information:
URL: | |
Reporter RHNID: | rajathacker |
Section | Windows Automation and Red Hat Ansible Automation Platform |
Issue description
Chapter 1
Section 1
Topic - Ansible Concepts and Architecture
Current Language in Paragraph 2 - The Ansible architecture is agentless. Typically, when you run an Ansible Playbook on Linux, the automation execution environment connects to the managed node by using SSH.
Improvised Language - The Ansible architecture is agentless. Typically, when you run an Ansible Playbook on Linux, Ansible connects to the managed node by using SSH (Which is default connection type for Ansible).
Reason - In Paragraph 1, Line 3 mentions - Your automation code might be processed directly on the control node or in a container-based automation execution environment.
It is ideal to keep the language generic, when in the previous paragraph we have identified both options.
Steps to reproduce:
Workaround:
Expected result: