We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ARI release 0.2.8 inline replace functionality is not performing as expected, ref below scenario: Input:
0.2.8
--- - name: Parse bgp summary ansible.utils.cli_parse: command: "show ip bgp summary" parser: name: ansible.netcommon.content_templates set_fact: bgp_health
Output:
- name: Parse bgp summary ansible.utils.cli_parse: command: show ip bgp summary parser: name: ansible.netcommon.content_templates
In above output --- yaml is missing, and also set_fact: bgp_health is not being replaced as expected after inline replace
---
set_fact: bgp_health
Input:
--- - name: Parse bgp summary ansible.utils.cli_parse: command: "show bgp summary" parser: name: ansible.netcommon.content_templates set_fact: bgp_health - name: Show Summary facts debug: msg: "{{ bgp_health }}"
- name: Parse bgp summary ansible.utils.cli_parse: command: show bgp summary parser: name: ansible.netcommon.content_templates set_fact: bgp_health - name: Show Summary facts ansible.builtin.debug:
As, in above output --- yaml syntax is replaced and debug msg is not being replaced as expected post inline replace functionality
msg
The text was updated successfully, but these errors were encountered:
No branches or pull requests
ARI release
0.2.8
inline replace functionality is not performing as expected, ref below scenario:Input:
Output:
In above output
---
yaml is missing, and alsoset_fact: bgp_health
is not being replaced as expected after inline replaceInput:
Output:
As, in above output
---
yaml syntax is replaced and debugmsg
is not being replaced as expected post inline replace functionalityThe text was updated successfully, but these errors were encountered: