chef-vault Fixed: Vault warns when valid JSON contains special character sequences

Description

Fixes an issue where Chef Vault writes a warning when a valid JSON document contains special character sequences, exposing sensitive vault data in the warning message.

Chef Vault should be agnostic to the content of the vault item JSON. It no longer inspects vault item contents, validation responsibility is left to the JSON parser to ensure the JSON data is valid.

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[ ] If Gemfile.lock has changed, I have used --conservative to do it and included the full output in the Description above.
[x] All new and existing tests passed.
[x] All commits have been signed-off for the Developer Certificate of Origin.

Nov 25 '24 22:11 decoyjoe

Additional context around this issue can be found in:

Nov 26 '24 17:11 decoyjoe

Hey @johnmccrae - I think this is related to powershell stuff?

Nov 26 '24 21:11 jaymzh

Just to keep people following this PR up-to-date, I followed up in Slack on this. The team is aware - but the pipelines here need some significant investigation to sort out. I've asked for a timeline estimate.

Feb 13 '25 17:02 jaymzh

https://github.com/chef/chef-vault/pull/435/files @jaymzh @decoyjoe fyi, I believe this is the work to fix the pipeline.