[9.4] [UII] Fix floating release badges and whitespace in integration policy editor (#264866)#265394
Merged
jen-huang merged 1 commit intoelastic:9.4from Apr 23, 2026
Merged
Conversation
…y editor (elastic#264866) ## Summary Resolves elastic#256854 This PR fixes the release badge (`Beta` label) not showing at the input title level for OTel packages (config needed to be expanded in order to see the label). While fixing that, I went down a bit of rabbit hole and found that the release badges and whitespace were just [odd](elastic#256854 (comment)) for input-only packages and single-stream inputs. _(Jen going down a UI rabbit hole? Groundbreaking...)_ I believe this was due to elastic#219287, elastic#254721, and maybe other PRs as part of elastic/ingest-dev#6979. So this PR ended up tweaking conditions for various spacers and flex groups, so that they render (or don't render) correctly. **I recommend reviewing this PR with whitespace turned off.** <img width="794" height="476" alt="image" src="https://github.com/user-attachments/assets/c5253f08-785c-4524-8590-776b0577b110" /> . <img width="800" height="569" alt="image" src="https://github.com/user-attachments/assets/c6cd619f-9179-4a22-89eb-60699b91a293" /> ## Testing Test the policy editor - both in standalone page and in add integration flyout (from agent policy) - with various packages that have GA and non-GA data streams, input-only integrations and regular ones, etc. I tested ones like these: - Azure Event Hub Input - Istio - Nginx OTel - Apache - etc... ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [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 - [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. (cherry picked from commit 8377aea) # Conflicts: # x-pack/platform/plugins/shared/fleet/public/applications/fleet/sections/agent_policy/create_package_policy_page/components/steps/components/package_policy_input_panel.tsx
botelastic
Bot
added
the
Team:Fleet
3 tasks
Contributor
|
Pinging @elastic/fleet (Team:Fleet) |
Contributor
ApprovabilityVerdict: Would Approve UI-only changes fixing visual issues with release badge positioning and whitespace in Fleet's integration policy editor. The changes adjust where badges are displayed based on input type and stream count, with comprehensive test coverage. No runtime behavior changes beyond presentation. Macroscope would have approved this PR. A repo admin can enable approvability here. |
MichelLosier
approved these changes
Apr 23, 2026
Contributor
💚 Build Succeeded
Metrics [docs]Async chunks
|
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
3 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.
Backport
This will backport the following commits from
mainto9.4:Questions ?
Please refer to the Backport tool documentation