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
[Fleet] use package storage when getting a package #85337
[Fleet] use package storage when getting a package #85337
Changes from 9 commits
5f9a770
dc5bc0b
2e7cde8
6e54ddf
54a3b7c
3e9ae7b
4186ba4
fe07c6e
83b3480
f16e5c3
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.
@skh I removed
input
being required in a policy template because it was causing all packages to fail during install or uninstall when getting theendpoint
package from storage.endpoint
does not have anyinputs
in itspolicy_templates
in its manifest.yml. Is the package correct or is the spec incorrect?inputs
will now be an empty array if there are no inputs in the manifest.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 you have it right. Let's follow spec as written and fix any bugs there
https://github.com/elastic/package-spec/blob/22bc835bcf0480c0973b2c6bbc86df1314e9c0ef/versions/1/manifest.spec.yml#L223
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.
In the parseAndVerify* methods I followed our existing types to decide which fields are mandatory. Spec and actual working package should take precedence though.