Skip to content

[Fleet] Fix broken maps icon key#88093

Merged
jfsiii merged 1 commit intoelastic:masterfrom
jfsiii:use-correct-ems-icon
Jan 14, 2021
Merged

[Fleet] Fix broken maps icon key#88093
jfsiii merged 1 commit intoelastic:masterfrom
jfsiii:use-correct-ems-icon

Conversation

@jfsiii
Copy link
Contributor

@jfsiii jfsiii commented Jan 12, 2021

PR Summary

Show emsApp icon from EUI if integration includes map assets.

Screen Shot 2021-01-12 at 3 14 14 PM

Looking at #62059 (comment), I believe it landed with the incorrect key at a time when that part of the page wasn't visible. When we enabled that section, we likely didn't notice the missing key since most integrations don't have Maps assets

Bug: master doesn't have an icon for Map assets

  1. Visit an integration with map assets, like AWS http://localhost:5601/app/fleet#/integrations/detail/aws-0.3.16
  2. Observe missing icon for Map in right column summary & HTTP request for /app/mapApp
    Screen Shot 2021-01-12 at 3 10 44 PM

This PR adds one

  1. Visit an integration with map assets, like AWS http://localhost:5601/app/fleet#/integrations/detail/aws-0.3.16
  2. Observe EMS icon is present in right column summary
    Screen Shot 2021-01-12 at 3 11 39 PM

@jfsiii jfsiii requested a review from a team January 12, 2021 20:27
@botelastic botelastic bot added the Team:Fleet Team label for Observability Data Collection Fleet team label Jan 12, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/ingest-management (Team:Ingest Management)

@jfsiii jfsiii self-assigned this Jan 12, 2021
@nchaulet nchaulet added the release_note:skip Skip the PR/issue when compiling release notes label Jan 12, 2021
Copy link
Contributor

@jen-huang jen-huang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this an issue in 7.11 too? If so, I'd consider this safe to backport to 7.11 too. Thanks for fixing!

@jfsiii
Copy link
Contributor Author

jfsiii commented Jan 12, 2021

@jen-huang I believe so, but I haven't confirmed. That's what I was thinking pinging @mostlyjason (and now @ph )

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@mostlyjason
Copy link
Contributor

I'd trust the eng team's judgement on the safety of this change

@jfsiii jfsiii added the bug Fixes for quality problems that affect the customer experience label Jan 13, 2021
@jfsiii
Copy link
Contributor Author

jfsiii commented Jan 13, 2021

@mostlyjason Seems quite safe to me. The icon this PR references has been in EUI for a few years, so it should work for everyone

I'll backport since it's a low-risk to add and rolling it back is also low effort/complexity.

@jfsiii jfsiii merged commit ca87bc4 into elastic:master Jan 14, 2021
jfsiii pushed a commit that referenced this pull request Jan 14, 2021
## PR Summary
Show [`emsApp` icon from EUI](https://eui.elastic.co/#/display/icons#apps) if integration includes map assets.

<img width="229" alt="Screen Shot 2021-01-12 at 3 14 14 PM" src="https://user-images.githubusercontent.com/57655/104367878-65628280-54e9-11eb-8d9c-fa838e2c15ae.png">

Looking at #62059 (comment), I believe it landed with the incorrect key at a time when that part of the page wasn't visible. When we enabled that section, we likely didn't notice the missing key since most integrations don't have Maps assets

## Bug: `master` doesn't have an icon for Map assets
 1. Visit an integration with map assets, like AWS http://localhost:5601/app/fleet#/integrations/detail/aws-0.3.16
 2. Observe missing icon for Map in right column summary & HTTP request for `/app/mapApp`
    <img width="1013" alt="Screen Shot 2021-01-12 at 3 10 44 PM" src="https://user-images.githubusercontent.com/57655/104367875-64c9ec00-54e9-11eb-81d8-982bec862f5f.png">

## This PR adds one
 1. Visit an integration with map assets, like AWS http://localhost:5601/app/fleet#/integrations/detail/aws-0.3.16
 2. Observe EMS icon is present in right column summary
    <img width="1087" alt="Screen Shot 2021-01-12 at 3 11 39 PM" src="https://user-images.githubusercontent.com/57655/104367877-65628280-54e9-11eb-91da-578fec6ff769.png">
jfsiii pushed a commit that referenced this pull request Jan 14, 2021
## PR Summary
Show [`emsApp` icon from EUI](https://eui.elastic.co/#/display/icons#apps) if integration includes map assets.

<img width="229" alt="Screen Shot 2021-01-12 at 3 14 14 PM" src="https://user-images.githubusercontent.com/57655/104367878-65628280-54e9-11eb-8d9c-fa838e2c15ae.png">

Looking at #62059 (comment), I believe it landed with the incorrect key at a time when that part of the page wasn't visible. When we enabled that section, we likely didn't notice the missing key since most integrations don't have Maps assets

## Bug: `master` doesn't have an icon for Map assets
 1. Visit an integration with map assets, like AWS http://localhost:5601/app/fleet#/integrations/detail/aws-0.3.16
 2. Observe missing icon for Map in right column summary & HTTP request for `/app/mapApp`
    <img width="1013" alt="Screen Shot 2021-01-12 at 3 10 44 PM" src="https://user-images.githubusercontent.com/57655/104367875-64c9ec00-54e9-11eb-81d8-982bec862f5f.png">

## This PR adds one
 1. Visit an integration with map assets, like AWS http://localhost:5601/app/fleet#/integrations/detail/aws-0.3.16
 2. Observe EMS icon is present in right column summary
    <img width="1087" alt="Screen Shot 2021-01-12 at 3 11 39 PM" src="https://user-images.githubusercontent.com/57655/104367877-65628280-54e9-11eb-91da-578fec6ff769.png">
@jfsiii jfsiii deleted the use-correct-ems-icon branch April 6, 2021 17:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Fixes for quality problems that affect the customer experience release_note:skip Skip the PR/issue when compiling release notes Team:Fleet Team label for Observability Data Collection Fleet team v7.11.0 v7.12.0 v8.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants