ansible/awx

Issue label for incompliance with Ansible

Open

#13,272 opened on Dec 2, 2022

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Python (3,333 forks)batch import
Hacktoberfestcommunitycomponent:docsgood first issuetype:enhancement

Repository metrics

Stars
 (13,071 stars)
PR merge metrics
 (Avg merge 24d 6h) (30 merged PRs in 30d)

Description

Please confirm the following

  • I agree to follow this project's code of conduct.
  • I have checked the current issues for duplicates.
  • I understand that AWX is open source software provided for free and that I might not receive a timely response.

Feature type

Enhancement to Existing Feature

Feature Summary

Existing incompliances of AWX with Ansible, make AWX quite difficult to use. Developing Ansible Playbooks, Roles and Collections following the Ansible Documentation to find out, they are not working in AWX.

Maybe there should be a list of incompliances documented somewhere? What about an issue label, which indicates incompliance issues?

Perhaps it should be explicitly specified in the AWX/Tower Docs, that the behaviour differs from Ansible.

Examples

#5926 #12364

Select the relevant components

  • UI
  • API
  • Docs
  • Collection
  • CLI
  • Other

Steps to reproduce

  1. Search the AWX Issue Labels for compliance, compliant, compatibility aso.
  2. Search the AWX/Tower Documentation for hints on differenciating behaviour to Ansible.

Current results

  1. The result list is empty
  2. None are found.

Sugested feature result

  1. An issue label, which clearly identifies known incompliances/incompatibilities of AWX with Ansible
  2. Find a hint, explicitly explaining, that behaviour differs from Ansible.

Additional information

No response

Contributor guide