WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Conversation

@Supplementing
Copy link
Contributor

Summary

Closes #242656

This PR removes the existing message about installing the integration on the settings page of a package when the user does not have the appropriate permissions to do so, and instead shows a callout letting them know that they don't have the required permissions. This is inline with the existing disabling of the installation button that already exists on the details page.

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

N/A

@Supplementing Supplementing requested a review from a team as a code owner December 10, 2025 21:45
@Supplementing Supplementing added release_note:skip Skip the PR/issue when compiling release notes backport:skip This PR does not require backporting Team:Fleet Team label for Observability Data Collection Fleet team labels Dec 10, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@Supplementing
Copy link
Contributor Author

Supplementing commented Dec 10, 2025

@sileschristian We didnt have an existing mockup for this callout, but I tried to align it with the one we use on the configs tab right next to this one. Please let me know if we need any adjustment. In the same token, @vishaangelova please take a look at the copy and let me know if it needs updating. Thanks in advance to you both!

@elasticmachine
Copy link
Contributor

elasticmachine commented Dec 10, 2025

💔 Build Failed

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #105 / Maps endpoints apis search ES|QL should return getColumns response in expected shape
  • [job] [logs] FTR Configs #105 / Maps endpoints apis search ES|QL should return getColumns response in expected shape

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
fleet 2.1MB 2.1MB +563.0B

History

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

Labels

backport:skip This PR does not require backporting release_note:skip Skip the PR/issue when compiling release notes Team:Fleet Team label for Observability Data Collection Fleet team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Fleet]: Required permissions are not available for Installing integration from Integration>Settings tab for User Role Agent policies: Read.

2 participants