-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Cloud plugin to handle new URLs #93436
Comments
Pinging @elastic/kibana-design (Team:Kibana-Design) |
I've labeled this with Kibana Design. I'll give it a go and reach out to Kibana Security (?) if I get stuck. |
As this is general Cloud / Kibana interaction as well, I don't think it could hurt to keep @joshdover and @thesmallestduck in the loop. Also @arisonl for awareness as this touches the user profile |
Cloud PR here: https://github.com/elastic/cloud/pull/77420 |
I've asked Yoel a question here on whether If it will no longer be passed, then it's going to require more involvement from other teams to convert existing usage and ought to be handled by engineers (as opposed to me). cc:/ @alexfrancoeur Currently, Kibana expects:
The new Cloud implementation is designed to send:
Things map as follows: The outliers: |
Good news :)
|
Hey @ryankeairns, I was just wondering what the target for this work is? I'd like to use |
Hey Yulia, 7.13, generally speaking. I have a draft PR started that I'll need some assistance on to get merged, but it's in the works. |
Thanks a lot for doing this, Ryan @ryankeairns! I'll follow the issue for updates, really looking forward to those additions to Cloud plugin. Let me know if I can help with the PR. |
Background
There is an existing capability of the
cloud
plugin that adds links to the user menu and left nav. These links do not appear as they were awaiting for URLs to be provided on the Cloud side. That time has come (see this Cloud PR) and, with that change and the passing of time, the final URLs have changed.Needed changes
Related work
cc:/ @alexfrancoeur
The text was updated successfully, but these errors were encountered: