Fix the flyout size issue#244072
Merged
saikatsarkar056 merged 5 commits intoelastic:mainfrom Nov 26, 2025
Merged
Conversation
saikatsarkar056
added
backport:skip
mdefazio
reviewed
Nov 25, 2025
Contributor
mdefazio
left a comment
mdefazio
left a comment
There was a problem hiding this comment.
A few comments. Thank you for picking this up! 🙌
x-pack/platform/packages/shared/security/api_key_management/src/components/api_key_flyout.tsx
Outdated
Show resolved
Hide resolved
x-pack/platform/packages/shared/security/api_key_management/src/components/api_key_flyout.tsx
Outdated
Show resolved
Hide resolved
yansavitski
approved these changes
Nov 25, 2025
yansavitski
approved these changes
Nov 26, 2025
Contributor
Author
|
@elasticmachine merge upstream |
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Async chunks
History
|
JordanSh
pushed a commit
to JordanSh/kibana
that referenced
this pull request
Dec 9, 2025
## Summary Fixes the API key flyout width by changing the size from m (medium) to s (small). ## Problem The API key flyout is too wide and extends beyond the recommended usage width, making the form appear stretched. ## Solution Changed the EuiFlyout size prop from "m" to "s" in the ApiKeyFlyout component. ## Testing - Navigate to Stack Management > Security > API Keys - Click "Create API key" - Verify the flyout is now narrower and fits within recommended width Closes elastic/search-team#11838 https://github.com/user-attachments/assets/9e03edf0-4256-4294-83df-2af6700933e8 ## Release note Fixes the API Creation Flyout sizing issue ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the API key flyout width by changing the size from m (medium) to s (small).
Problem
The API key flyout is too wide and extends beyond the recommended usage width, making the form appear stretched.
Solution
Changed the EuiFlyout size prop from "m" to "s" in the ApiKeyFlyout component.
Testing
Closes elastic/search-team#11838
Screen.Recording.2025-11-24.at.2.58.33.PM.mov
Release note
Fixes the API Creation Flyout sizing issue
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesbackport:*labels.Identify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.