added changes to fix the client run search #7076

vinay033 · 2022-05-25T10:27:31Z

Signed-off-by: Vinay Sharma vsharma@chef.io

🔩 Description: What code changed, and why?

As an Automate user when I type a node name to search for in the infra runs tab or compliance, it will return only an exact match. In the compliance tab, it's working fine but in the case of client run, it's showing a list of all the nodes.

⛓️ Related Resources

https://chefio.atlassian.net/browse/STALWART-123
https://github.com/chef/customer-bugs/issues/675

👍 Definition of Done

I have added some changes to the elastic search query to make this search consistent.

👟 How to Build and Test the Change

to test these changes, you need to add the sample data first

# to load the sample data in the client run
chef_load_nodes

# to load the sample data in compliance
chef_load_compliance_nodes

after adding the data you need to rebuild the config management service 
rebuild components/config-mgmt-service/

✅ Checklist

All PRs must tick these:

I have read the CONTRIBUTING document.
All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)