Bug 1374467

As an update, I'm comfortable with changing out AND for an actual operator (&& or something else based on the development constraints)

Additional example from my actual workflow.

Project 'Dune' has systems in Lifecycle Production and Lifecycle Integration.

Integration systems are in a hostgroup ".../Dune/Integration", where Dune is a parent host group
Production systems are in a hostgroup ".../Dune/Production", where Dune is a parent host group

All hosts use the same content view.

I wish to set a class parameter for all Integration systems for Dune.

I cannot base it on Lifecycle, as that would catch other projects.
I cannot base it on Content View, as that would also catch production
I cannot base it on Host group, as only the top most group is captured (in this case Integration or Production).

From a UI vs parsing out operators (did the user literally mean && or?) perhaps adding a + to the end of the line to add an additional matcher box under the current one prefixed by an i18n *and* would provide a clean interface and avoid strange parsing behavior.

This already exists, it's possible to create a matcher like: 

fqdn, osmajorrelease
with the value:
host.example.com, 7

and that will create what you requested.
The comma creates an AND condition.

Per comment 5, moving to ON_QA for verification and testing.

fqdn, osmajorrelease = host.example.com, 7

does not appear to function in my environment.  Is there some other syntax that should be used in place of '='?

In the order put: fqdn, osmajorrelease
then the matcher:
fqdn = host.example.com, osmajorrelease = 7
and the value you wanted.

Use of:

fqdn = host.example.com, domain = example.com

Produces the following error:

fqdn=host.example.com,domain=example.com does not match an existing host


Where host.example.com is a host that is attached to Sat6 and example.com is a valid domain.

Individually, fqdn = host.example.com and domain = example.com can both be set as matchers without error.

Screenshot attached

Created attachment 1207644 [details]
error message screenshot

The error is a bug that is already fixed in 6.2.

Change the order and put domain first so it would be: domain = example.com, 
fqdn = host.example.com.

Also, in the screenshot it looks like the order does not contain: domain,fqdn which should be there to work.
It's not enough to have each of them in the order, you need to add them together.

I'll see about getting a 6.2 update on my schedule.

fqdn and domain are separately in the Order list.  I take it from your comment a line with the exact text "domain,fqdn" needs to be added.

I wasn't able to find any of this information in the official doc.

Yes the exact text needs to be added.
The docs might need an example for multiple matchers.
Does this work for you?

The behavior I need is present once the listed changes are deployed.

Can we get a high priority doc update in motion?  This behavior is super handy.

Hello


These changes are now live on the customer portal. 

For example:
https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/host-configuration-guide/82-parameters#sect-Red_Hat_Satellite-Host_Configuration_Guide-Configuring_Smart_Variables

Thank you