-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
Adds link for Cloud deployment settings #66486
Conversation
d016513
to
dc53e8c
Compare
Ping @elastic/kibana-core-ui for review on header components |
dc53e8c
to
34824f9
Compare
/** | ||
* Override the current set of custom nav link | ||
*/ | ||
setCustomLink(newCustomLink?: ChromeCustomLink): void; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not more extendable version:Chrome CustomLink[]
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After discussing with @ryankeairns, we didn't want to allow for multiple links to be registered by plugins and potentially flood the left nav. This is also a temporary addition to the collapsible nav to provide cloud users a link that redirects them to the cloud console and should really only be used by the cloud plugin until the redesign work in #65787 relocates this link.
Catherine and I just talked over slack and came up with a plan to move away from using a new
Reusing @elastic/kibana-platform Shout out if this doesn't seem right to y'all and if you'd prefer to see a new type added for this after all. |
@myasonik As long as this doesn't mean introducing additional fields to |
34824f9
to
834d03c
Compare
@cqliu1 similar to the Cloud profile links PR, can you provide a snippet for the |
@ryankeairns Sure! All you need to do is a define a cloud ID and a deployment url in your kibana.dev.yml like this:
|
The UI design looks good; sample config works as expected. |
Accesses deploymentUrl config property Added i18n support for deployment link Resolved merge conflict Use existing ChromeNavLink type Added external link option to createNavLink
7d2a068
to
33fa8fb
Compare
Co-authored-by: Michail Yasonik <michail@yasonik.com>
… cloud-deployment-link
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested it out, looks and works as expected!
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, as long a showing the link only in modern
nav mode is the expected behavior.
if ( | ||
!externalLink && // ignore external links |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NIT: by using the new navigateToUrl
API instead of navigateToApp
, we could get rid of this additional check and externalLink
parameter. But platform can do it later.
@elasticmachine merge upstream |
@elasticmachine merge upstream |
Co-authored-by: Michail Yasonik <michail@yasonik.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
💚 Build SucceededBuild metricspage load asset sizebeta
History
To update your PR or re-run it, just comment with: |
Summary
Closes #65089.
Related to https://github.com/elastic/cloud/issues/57690.
This adds a link to the Cloud deployment page to the left nav when the cloud plugin is enabled, i.e Kibana is running on cloud. This link will show for all Kibana users on cloud, but only cloud users that authenticate with admin privileges to their cloud deployment will be able to access the cloud deployment page.
Note: This is a temporary solution for redirecting Cloud users from Kibana back to the Cloud console. This component will be removed in favor of the redesign work described in #65787.
To test
You can mock enabling the cloud plugin locally by defining a cloud ID and deployment url in your
kibana.dev.yml
, like so:Checklist
Delete any items that are not applicable to this PR.
For maintainers