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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[IM] add screenshot detail view and image endpoint #48149
[IM] add screenshot detail view and image endpoint #48149
Changes from all commits
f4d07c8
409636a
db9240f
3f4e3d6
4501956
5385188
8506725
d075fb6
9f7cafe
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I might even putting it inline
but not a big deal to define as
API_IMG_PATTERN
or declare inlineThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why don't we use here the direct path to the screenshot from the manifest? An example can be found here: http://integrations-registry.app.elstc.co/package/auditd-2.0.4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ruflin are you saying to just link directly to the registry like: http://integrations-registry.app.elstc.co/package/auditd-2.0.4/img/screenshots/auditbeat-file-integrity-dashboard.png? Otherwise, this route handles both the icon and screenshot images, which have slightly different paths, using the integrations manager api.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I think I got what I missed here. These are the routes for the internal calls. What I worry is that we for example have
/img
hardcoded, so if we decide to move images undermedia
, things break. That is the reason manifest we always have the full relative paths, so images can be put where the package creator prefers to put them.But lets ignore it for now and move forward.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ruflin I see. Would you have used the file extension (svg, png) for the route instead to differentiate it from other assets?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for catching that @ruflin.
@neptunian let's merge this as-is then do a follow-up where we replace the specific image route, with a new route (alter info route) that is essentially a pass-through/proxy to the registry.
then do a similar process to what you do now with the image where we call the registry and return the response & appropriate headers