Added included policyfile details info. #5398

himanshi-chhabra · 2021-07-30T11:54:39Z

Signed-off-by: Himanshi Chhabra hchhabra@progress.com

🔩 Description: What code changed, and why?

Add included Policy file details page
Add revision button on included policy file slider

⛓️ Related Resources

#5246

👍 Definition of Done

Added included Policy file details page in slider and Go to policyfile details page button
Added revision button on included policy file slider
Added cypress test cases for the detail page.

👟 How to Build and Test the Change

PFA Video

STEP 1
inside the hab studio

[default:/src:0]# build components/automate-ui-devproxy/
[default:/src:0]# start_automate_ui_background
[default:/src:0]# start_all_services

STEP 2
open new window
go to automate UI path

$ cd components/automate-ui
and run the command 

npm run serve:hab

To add data https://github.com/chef/automate/blob/master/dev-docs/adding-data/adding_test_data.md#adding-data-to-infra-views
Steps for policy file tab:

Go To Infrastructure -> Chef Servers -> click server name-> click on org name -> policyfile tab.
Will see the policy file if available else will see no preview.
if available click on policy file name -> will see details page
click on Included Policy file accordion -> List of included Policy -> click particular included policy file
Opens a slider that contains if API is correct then :
a) meta info of included policyfile
b) Go to policyfile details page button -> click -> go to details page
c) Revison list Button -> click opens new slider which contain list of revision id.
Opens a slider that contains if API is not correct then :
a) Customized notification
b) No preview image.
c) Disabled Go to policyfile details page button

✅ 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)