fix: handle policies as a string #205
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.
This pull request enhances the handling of policy data in the agent's configuration manager by adding support for YAML-formatted policy payloads. When a policy is received with its data as a YAML string, the code now attempts to unmarshal it into a structured map before passing it to the policy manager. Comprehensive tests have been added to ensure correct behavior for various input scenarios, including YAML strings, structured data, empty or invalid YAML, and non-YAML formats.
Policy Data Handling Improvements:
handleAgentPoliciesto detect YAML-formatted policy data provided as a string, unmarshal it into a map, and handle errors gracefully by logging a warning and falling back to the original data if unmarshaling fails (agent/configmgr/fleet/from_rpc.go).gopkg.in/yaml.v3package to support YAML unmarshaling (agent/configmgr/fleet/from_rpc.go).Testing Enhancements:
agent/configmgr/fleet/from_rpc_test.go).