> What is the nature and description of the request?
It would be beneficial in Ansible to have some checkbox/toggle button that allows us to switch on/off case sensitivity. This should default to case-sensitive for backwards compatibility. I'm aware this can be done with inline regex modifiers (?i) at the limit, but some CI/CD pipelines or integrations may errantly override the entire limit and not re-implement the case insensitivity flags for regex.

> Why does the customer need this? (List the business requirements here)
We have several products that integrate with each other: Zabbix, Ansible Automation Platform, RH Insights, DNS Servers (bind), and our authentication system (unspecified for this purpose). Zabbix hooks into Event-Driven Ansible via a webhook, and Ansible syncs our host inventory from RH Insights. Occasionally, the hosts will register in different products with different characters cases. So Zabbix may have registered: "host" by RH Insights sees "HOST". When Zabbix webhooks into EDA, the limit declaration in our template execution causes the playbook to fail because "Specified inventory, host pattern and/or --limit leaves us with no hosts to target." BIND (our internal DNS resolvers) are inherently case insensitive, so they would resolve the request, if Ansible were to send it. BIND remains RFC compliant for DNS resolution purposes.

FYI...Please see the two TXT files which demonstrates the behaviour with case-sensitive matching (assuming I don't specify the inline modifier)

> How would you like to achieve this? (List the functional requirements here)
Create a checkbox or toggle button in the AAP UI that toggles case-sensitive searches when specifying a limit in the UI. If done through the CLI, this could be an additional flag (eg: "ansible-playbook [...] --limit host --case-insensitive") This could be done "under the hood" by prepending the string (in quotes) "~(?i)" to any specified limit. When dealing with Ansible Rulebooks via EDA, create an option in the payload option under job_args that is optional called "case_sensitive" with a boolean value of true/false/yes/no/0/1

FYI...See attached for some screenshot examples (RH Ansible UI under the template section), and an example of what this might look like in an EDA Rulebook.