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.

Sign up for GitHub

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

Jump to bottom

[Fleet] Test agent config modification side effects #81623

Closed
nchaulet opened this issue Oct 26, 2020 · 1 comment · Fixed by #81661
Closed

[Fleet] Test agent config modification side effects #81623

nchaulet opened this issue Oct 26, 2020 · 1 comment · Fixed by #81661
Assignees
@nchaulet
Labels
Team:Fleet Team label for Observability Data Collection Fleet team technical debt Improvement of the software architecture and operational architecture

Comments

@nchaulet
Copy link
Member

Description

Fleet rely heavily on the POLICY_CHANGE action to exists and to be correctly created to distribute the correct policy to agents.

This action is created each time a config is modified, settings change, an input is modifed...

We should add tests to ensure that action is correctly created each time.
@nchaulet nchaulet added technical debt Improvement of the software architecture and operational architecture Team:Fleet Team label for Observability Data Collection Fleet team labels Oct 26, 2020
@nchaulet nchaulet self-assigned this Oct 26, 2020
@elasticmachine
Copy link
Contributor

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

@nchaulet nchaulet mentioned this issue Oct 26, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nchaulet nchaulet

Labels
Team:Fleet Team label for Observability Data Collection Fleet team technical debt Improvement of the software architecture and operational architecture
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Fleet] Test creating|copying a policy create a correct POLICY_CHANGE action nchaulet/kibana
2 participants
@nchaulet @elasticmachine