storage service edit mode: check which attached resources are compliant to selected capabilities

[OrGur1987]

issue: ManageIQ/manageiq-ui-classic#8749

added button in service edit mode which enables user to check what currently attached resources will comply with the selected capabilities.

this PR adds the action to the api controller and to api.yml

• note that it is based on the yet to be merged storage service edit #1216, and should be rebased on master after that is merged.

[OrGur1987]

@miq-bot cross-repo-tests ManageIQ/manageiq#22450

[OrGur1987]

cross repo passed:
ManageIQ/manageiq-cross_repo-tests#774

[OrGur1987]

@miq-bot cross-repo-tests ManageIQ/manageiq#22450

[OrGur1987]

@bdunne @kbrock
ready for review, thanks

[OrGur1987]

@miq-bot cross-repo-tests ManageIQ/manageiq#22450

[OrGur1987]

hi @agrare,
@jeffibm merged the ui for this issue

[kbrock]

definitely want to use id and not _id

Also, do we want data["id"] or is that underscore correct?

[OrGur1987]

no problem changing the method param name to id, but changing the data hash key to id raises the following error in api_ems_resource: Resource id or href should not be specified for creating a new storage_services.

perhaps I shouldn't have used api_ems_resource if it's intended for creating new records only?
I used it because it appeared in the existing validate action that I based upon:

manageiq-api/app/controllers/api/physical_storages_controller.rb

Line 26 in e198086

def validate_resource(type, _id = nil, data = {})

is there an alternative?

if data["_id"] can stay that way, I prefer using api_ems_resource since things are working right now..

thanks

[miq-bot]

Checked commit Autosde@8b1dc51 with ruby 2.6.10, rubocop 1.28.2, haml-lint 0.35.0, and yamllint
1 file checked, 0 offenses detected
Everything looks fine. 🍰