Skip to content
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] Allow Package ID in Create Package Policy requests #100897

Closed
kpollich opened this issue May 28, 2021 · 1 comment · Fixed by #100908
Closed

[Fleet] Allow Package ID in Create Package Policy requests #100897

kpollich opened this issue May 28, 2021 · 1 comment · Fixed by #100908
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@kpollich
Copy link
Member

See #99866 (comment)

We expose the package ID at the /api/fleet/epm/packages?experimental=true endpoint, e.g.

Screenshot

Screen Shot 2021-05-28 at 10 19 58 AM

For E2E tests (see linked comment) that use this payload and include the id, and error is throwing upon package policy creation:

{"statusCode":400,"error":"Bad Request","message":"[request body.package.id]: definition for this key is missing"}

Our schema definition for this policy creation request forbids id in the request body. This should be changed to allow for the id field's presence.

@kpollich kpollich added bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team labels May 28, 2021
@kpollich kpollich self-assigned this May 28, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

kpollich added a commit to kpollich/kibana that referenced this issue May 28, 2021
Add `id` field for packages in info/create requests

Closes elastic#100897
kpollich added a commit to kpollich/kibana that referenced this issue May 28, 2021
E2E tests are failing because they include the ID field returned by the
package list endpoint. This just updates our request schema to accept an
ID, though we don't persist or deal with the ID anywhere.

Closes elastic#100897
kpollich added a commit that referenced this issue Jun 1, 2021
E2E tests are failing because they include the ID field returned by the
package list endpoint. This just updates our request schema to accept an
ID, though we don't persist or deal with the ID anywhere.

Closes #100897

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
kibanamachine added a commit to kibanamachine/kibana that referenced this issue Jun 1, 2021
E2E tests are failing because they include the ID field returned by the
package list endpoint. This just updates our request schema to accept an
ID, though we don't persist or deal with the ID anywhere.

Closes elastic#100897

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
kibanamachine added a commit that referenced this issue Jun 1, 2021
E2E tests are failing because they include the ID field returned by the
package list endpoint. This just updates our request schema to accept an
ID, though we don't persist or deal with the ID anywhere.

Closes #100897

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>

Co-authored-by: Kyle Pollich <kyle.pollich@elastic.co>
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 Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants