-
Notifications
You must be signed in to change notification settings - Fork 189
Add agent_policy_id and policy_revision_idx to checkin requests #9931
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
base: main
Are you sure you want to change the base?
Add agent_policy_id and policy_revision_idx to checkin requests #9931
Conversation
Adding integration/e2e tests requires the fleet-server to be implemented first: elastic/fleet-server#5501 |
Add the agent_policy_id and policy_revision_idx attributes to checkin requests.
39f169e
to
0721e6f
Compare
0721e6f
to
cfb5df4
Compare
|
||
// Ack sends an ack for the associated action if the results are expected. | ||
// An ack will not be sent for a POLICY_CHANGE action, but will be when this method is used by UNENROLL actions. | ||
func (l *policyChange) Ack() error { |
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.
It may be less confusing to make this a nop, and provide something else for unenroll actions to use
|
What does this PR do?
Add the agent_policy_id and policy_revision_idx attributes to checkin requests.
These attributes are sources from the action stored as a part of the state.
Why is it important?
The policy information in fleet-server and agent may go out of sync; this may occur in cases where a VM restores from a snapshot.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration files./changelog/fragments
using the changelog toolDisruptive User Impact
N/A
Related issues