Description
Thank you very much for providing this example for developing dynamic plugins for the console. We were able to learn a lot from it and felt comfortable to start experimenting with this new feature.
The below project is a fork of this sample plugin we wrote to showcase our struggles with extending Route actions in OpenShift 4.10.20 using the console.action/resource-provider extension point.
https://github.com/BWagenerGenerali/route-action-plugin
We have closely mirrored the structure of a static plugin (console-app) which adds such extension points to Deployments and DeploymentConfigs etc.
Doing so we have successfully added actions to the context menu of DeploymentConfigs, however the same exact configuration wouldn't work for Routes.
We do understand that for OpenShift 4.10 dynamic console plugins have tech preview maturity. However we are still curious to hear whether there is something we are missing as to why routes wouldn't be supported as a target of the console.action/resource-provider extension point or whether dynamic plugins are just not there yet implementation wise.
All changes we made are visible in this commit diff main...BWagenerGenerali:route-action-plugin:main
Most importantly we configured two extension points, one for DeploymentConfigs and one for Routes: console-extensions.json, both with the same codeRef. The one for DeploymentConfigs works, the one for Routes does not.
It would be great if you could check out our sample or confirm whether extending Routes using console.action/resource-providers is within the scope of customization using dynamic plugins (or whether it will be in the future).