[Fleet] Fix agent policy change action migration #79046
Merged
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.
Summary
Follow up to #78221. In that PR, saved object migrations was added for agent policy change actions to support the renamed fields, but
data
field is encrypted so the migration did not work fully.This PR fixes that by using EncryptedSavedObject plugin's
createMigration()
so that the encrypteddata
field can properly be read, parsed, and restructured.I tested this by comparing the response of the agent checkin endpoint (which returns decrypted unacknowledged actions) between
7.9
branch and this PR branch. I seeded the data using 7.9 and the migrations kicked in properly after switching versions: