ascli config preset set <preset> private_key @val:@file:<path to key> writes the contents of the key to console and into the config.yaml #185
Description
We follow the documentation and do something like
ascli config preset set my_aoc_org private_key @val:@file:"$HOME/.aspera/ascli/my_private_key"
to save the path to the key in config.yaml.
After updating to 4.20 from 4.11, we have started noticing this in the console output of that command:
Updated: my_aoc_org: private_key <- -----BEGIN RSA PRIVATE KEY-----
<actual private key content>
-----END RSA PRIVATE KEY-----
Saving config file.
which is not great. The key also seems to be getting written into the config.yaml instead of the path to the key.