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.
This change implements support for lists of secret values in fleet integration policies. There are two ways a secret value can be defined:
"password": "secret"<->"password": {"id": "Zgr3ZJgBz9OcmZgWR1vo", "isSecretRef": true}"hosts" : ["root:test@tcp(127.0.0.1:3306)/"]<->"hosts": {"ids": ["Zgr3ZJgBz9OcmZgWR1vo], "isSecretRef": true}The code now correctly maps between both cases. (It used to only handle the simple string)
The bug report actually contains a second bug that shows when using
vars_json = "{}",. Since the API always responds with anilvalue, it generates a diff between the config and the actual state. The solution here is to mapnilto"{}"if the local config contains"{}".