Subscriptions link for UI actions and connectors should go to enterprise page for ECK

[peterschretlen]

• In Dynamic uiActions & license support #68507 we check the license level on UI actions and offer a "get more actions" link
• In License checks for actions plugin #59070 we check the license level on connectors and actions for alerting, and offer a similar "subscription plans" link.

Both links go to https://www.elastic.co/subscriptions
But when running in ECK they should direct the user to https://www.elastic.co/subscriptions/enterprise page

I don't consider it a priority issue but logging it for tracking. Since we have now two places with this URL hardcoded and it changes by product, we may want to find a central place for it at a minimum, and find a way to configure it.

Connectors UI:

UI Actions:

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

[elasticmachine]

Pinging @elastic/kibana-app-arch (Team:AppArch)

[pmuellr]

Thinking it probably makes sense to make that link configurable, with a default of https://www.elastic.co/subscriptions - and then we would arrange to override it in the ECK config (I assume there would be a way to do that).

If alerting is the only affected component, it could be an alerting specific config, but ... that doesn't feel right - I'd imagine other apps / solutions will eventually want these links as well.

[Dosant]

@elastic/kibana-platform, do you think this dynamic link should become a part of licensing plugin? Or maybe part of docLinks to be available in OSS?

[pgayvallet]

If the link target only got two possible values, and only depends on whether kibana runs on ECK or not, it could be possible to add the link in the docLink service and handle the switch internally/automatically.

@joshdover WDYT? Do we want to be aware of our running environment from within core? If we do, we need to have a way to know if we are running on ECK in core, as the information is currently only available from the cloud plugin

[Dosant]

FYI: one more occurrence: #79045

[gmmorris]

pinging @lukeelmers :)

Looking at this backlog item looks like it's on hold for us to decide if this can be managed via the docLink.
If this is the case, I'd ideally like to mark this as blocked for our team until that need is addressed at core level.
If this isn't the case, then we can look at how we might solve this at another level 🤔

[ppisljar]

Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment.