Specifying CONNECTION_NAME.DATASET.TABLE for result handler results in parameters including passwords in config files

[tarora-clgx]

Is your feature request related to a problem? Please describe.
I am working on setting up DVT for ~600 tables. In QA we are executing each of these and generating yaml config files so we can run those in higher environment to keep our validation logic consistent. I have results handler on postgres which is also my target connection. so i define my -rh as target_conn.pso_data_validator.results.
When generating the config YAML files using --config-file option, i noticed that yaml file has hardocded all connection param values including password of the target_conn for the results handler. I have run this w/o providing a results handler string, it does not do it for source and target connection. At this point I am unable to load all my config files to github because of the hardcoded password.

What version of DVT are you using?
8.1.1

What type of connections are you using for source and target?
oracle for source, postgres for target

Describe the solution you'd like
Output YAML file generated using "-c" option should have results handler point to connection name and not its individual values similar to it working for source and target connection.
Note: This connection is created using the connections -add option.

Describe alternatives you've considered
Setting up via BigQuery but my results data is not huge since i am only collecting failed results. It is quicker to set up with psotgres.

How are you executing DVT?
on prem

Additional context
Add any other context or screenshots about the feature request here.

[smpawar]

[sundar-mudupalli-work]

Thank you.

I am able to reproduce the issue in our environment. The specific feature - Postgres result handler PR 1480 was added recently.

Thank you for bringing this to our attention

Sundar Mudupalli