Open cvignola opened 5 years ago
We will make progress on this issue in a simple way, by adding labels to resources that enable/disable corresponding actions on the UI action menu - see issue #37. In the future it would be desirable for containers to expose capabilities (using a method TBD) and then transferring those labels to activate actions, using the method prescribed in issue #37.
required: a way to determine intersection between a) available actions by kind in UI and b) advertised/supported actions by resource instance
practical example: open liberty deployment can support actions a,b,c compared to a open liberty instance (container) that supports only actions a & b -> result is that menu shows only actions a & b for that resource (deployment) instance.