Filter by variables lacks resolved variables

[Sulochan Acharya]

Currently filtering by variables like region?vars=a:b lacks the ability to search for resource by resolved vars.

We need a way to include resolved vars in the search path, but allow users to choose if the search should include resolved var, similar to what we do with vars in general with --resolved=true/false

so search might look something similar to:

region?vars=a:b&resolved=true

[Jim Baker (jimbaker)]

This impacts being able to use variables for searching, especially in combination at different levels. Should be a straightforward fix.

[Jim Baker (jimbaker)]

Also by default, I think we should assume resolved=true, much as we do with hosts now.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/440929

[Jim Baker (jimbaker)]

Addressed by https://review.openstack.org/#/c/440929/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/440929
Committed: https://git.openstack.org/cgit/openstack/craton/commit/?id=3d0506b69c255571ee6b580f85a0bf6646d7ed21
Submitter: Jenkins
Branch: master

commit 3d0506b69c255571ee6b580f85a0bf6646d7ed21
Author: Jim Baker <email address hidden>
Date: Thu Mar 2 21:56:28 2017 -0700

    Variable search for resources now uses resolved variables.

    Implements a filter addition for vars such that each key-value pair in
    the vars is searched for a possible match, regardless of associated
    resource; then chases the associated resources for the specific
    resource being searched for, thereby implementing the resolution
    algorithm (but in reverse). Finally all such resources are checked to
    see if they intersect with respect to their rooting key-value pairs in
    the original search.

    Examples:

    $ GET v1/hosts?vars=openstack_release:juno

    $ GET v1/hosts?vars=foo:abc,bar:xyz

    To disable this feature in your request, you can supply
    'resolved-values=false', for example:

    $ GET /v1/hosts?vars=foo:bar,baz:zoo&resolved-value=false

    Filter values are not currently encoded for JSON; but this will fixed
    in a subsequent patch that is addressing generalized JSON matching via
    JSON path.

    Change-Id: I1d40d734e60b5563dfb01da05ffb6494ed9a919c
    Closes-bug: 1661226
    Closes-bug: 1669493