Skip to content

Fix to show the security rule name in the integration assets accordion#272089

Open
chrisberkhout wants to merge 1 commit into
elastic:mainfrom
chrisberkhout:security-rule-name-in-accordian
Open

Fix to show the security rule name in the integration assets accordion#272089
chrisberkhout wants to merge 1 commit into
elastic:mainfrom
chrisberkhout:security-rule-name-in-accordian

Conversation

@chrisberkhout
Copy link
Copy Markdown

@chrisberkhout chrisberkhout commented Jun 1, 2026

Summary

Fix to show the security rule name in the integration assets accordion.

Security rule object don't have a title, they only have a name. Use the name field if there's no value in title.

Screenshot of the problem:

image

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

  • Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
  • Documentation was added for features that require explanation or tutorials
  • Unit or functional tests 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
  • 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 was used on any tests changed
  • The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
  • Review the backport guidelines 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.

Security rule object don't have a title, they only have a name. Use the
name field if there's no value in title.
@chrisberkhout chrisberkhout self-assigned this Jun 1, 2026
@chrisberkhout chrisberkhout requested a review from a team as a code owner June 1, 2026 09:57
@chrisberkhout chrisberkhout added release_note:fix Team:Fleet Team label for Observability Data Collection Fleet team backport:all-open Backport to all branches that could still receive a release labels Jun 1, 2026
@infra-vault-gh-plugin-prod
Copy link
Copy Markdown

Pinging @elastic/fleet (Team:Fleet)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:all-open Backport to all branches that could still receive a release release_note:fix Team:Fleet Team label for Observability Data Collection Fleet team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant