Using 'rm -v' causes integration with argocd to fail.

[PatrickSplice]

This is a bit of a nitpick, but in the secrets.sh file, the command to remove the temp decrypted file uses 'rm -v', which prints out "removed 'secrets.yaml.dec."
# cleanup on-the-fly decrypted files [[ ${#decfiles[@]} -gt 0 ]] && rm -v "${decfiles[@]}"

The argocd gitops tool will support helm plugins, but it is currently up to the user to include them in a custom docker build. I was able to do that, but for some reason my build kept puking with a json unmarshal error.
Source: mongodb/templates/prometheus-service-monitor.yaml\n\n\n---\n# Source: mongodb/templates/pvc-standalone.yaml\n\n\n---\n# Source: mongodb/templates/svc-standalone.yaml\n\n\nremoved 'secrets.yaml.dec'\n" duration=446.253888ms execID=5Xw1G time="2020-11-18T21:05:11Z" level=error msg="finished unary call with code Unknown" error="failed to unmarshal manifest: error unmarshaling JSON: while decoding JSON: json: cannot unmarshal string into Go value of type map[string]interface {}" grpc.code=Unknown grpc.method=GenerateManifest grpc.request.deadline="2020-11-18T21:06:10Z" grpc.service=repository.RepoServerService grpc.start_time="2020-11-18T21:05:10Z" grpc.time_ms=1004.918 span.kind=server system=grpc

When I turned on.debug logging, I saw that message from the secrets.sh included in the manifest output from the "helm secrets template" command run by argocd. I included a sed to change it to a simple rm and that solved my problem.
# cleanup on-the-fly decrypted files [[ ${#decfiles[@]} -gt 0 ]] && rm "${decfiles[@]}"