We had the case, that sensitive data wasn't masked correctly. We have a Docker config JSON which contains multiple quotes in a field.
Example:
{\"auths\":{\"https://some-registry.io\":{\"username\":\"docker-pull\",\"password\":\
would result in
=> "**"auths\":{\"https://some-registry.io\":{\"username\":\"docker-pull\",\"password\":\
now results in
=> "*******************************************************************************************"
We had the case, that sensitive data wasn't masked correctly. We have a Docker config JSON which contains multiple quotes in a field.
Example:
{\"auths\":{\"https://some-registry.io\":{\"username\":\"docker-pull\",\"password\":\
would result in=> "**"auths\":{\"https://some-registry.io\":{\"username\":\"docker-pull\",\"password\":\
now results in=> "*******************************************************************************************"
This PR fixes this. Provided tests have been run.