Disabled edit button if databag item is encrypted.

[himanshi-chhabra]

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

🔩 Description: What code changed, and why?

Need to disable the edit button if we have data bag item as encrypted

⛓️ Related Resources

#5045

👍 Definition of Done

Disabled edit button if we have data bag item as encrypted

👟 How to Build and Test the Change

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
To add encrypted databag :

1. inside hab studio run local dev server:

   • start_chef_server
   • infra_service_load_chef_repo
   • converge_policyfile_chef_client

2. inside chef-workstation:
   go to chef-startef/ chef-repo folder then run these commands:
   - openssl rand -base64 512 | tr -d '\r\n' > ~/encrypted_data_bag_secret
   - knife data bag create admins
   - knife data bag create admins encrypted-test --secret-file ~/encrypted_data_bag_secret
   - in nano file add "password": "roots" -> then CTRL+o , CTRL +x

3. In UI:

   • Go To Infrastructure -> Chef Servers -> click server -> click org -> go to databag tab -> click admins -> click encrypted-test -> edit button is disable.

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

All PRs from Progress employees should tick these if appropriate:

• Tests added/updated? (all new code needs new tests)
• Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.

📷 Screenshots, if applicable

data-bag-encrypted.mp4

[netlify]

👷 Deploy Preview for chef-automate processing.

🔨 Explore the source changes: 7b8a6b0

🔍 Inspect the deploy log: https://app.netlify.com/sites/chef-automate/deploys/6148709854ff480008826666

[vinay033]

good work 👍🏻

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[chaitali-mane]

LGTM, Thanks @himanshi-chhabra