Resolve CE-2153 "Disabling controll buttons"

Disabling control buttons in order to prevent accidental double action-run (like deployment, undeployment,...)

requested review from @alexandermadsen, @christinajenks, and @domonkosgulyas

assigned to @imretoth

Solution is deployed to DEMO environment - if someone would like to check the result.

Looking good!

Could we add the HostDetails page as a story so that we can test in storybook?

I think also that the Modify IOC button in IOCDetailAdmin was missed

added 1 commit

• 6810162a - Fix missing disabling button calls for certain functions

Compare with previous version

added 24 commits

• 6810162a...447e46c8 - 20 commits from branch develop
• f33ae401 - CE-2153: Disabling controll buttons
• d8918421 - Modifying button disable functions
• d2d22df8 - Modifying button disabled function
• ff47270c - Fix missing disabling button calls for certain functions

Compare with previous version

Can you please still add the HostDetailsView as a story? Thanks! (Note, you will probably need to add a few more stubbed endpoints to the mock api)

@christinajenks are you sure I should implement the HostDetailsView story in this ticket? There are no buttons to enable/disable. On the other hand IocDetailsView has control elements, but on every tab there are lot of requests to be mocked (ProcServLog, host information, Prometheus requests, User level,...) and the buttonDisabled property is only declared/set on a deeper level on the component tree.

We should eventually have a way to test these isolated cases without relying on the backend. If it's too much right now then we should create a followup to address it then...I just really don't like how we need to manually verify things on a system that can impact prod by accident. :/

approved this merge request

Thank you for the review! And agree, we should come up a better way to have storybook(s) for the IOCDetails view to check certain modifications!

mentioned in commit 7e1f3ad3

merged