Potential Conflict with Generic Secret Path Name in ~/.secrets.json

harness / harness-cli

Harness CLI for managing Harness resources, from the command line using YAMLs as input [LIMITED GA]

MIT License

12 stars 12 forks source link

Potential Conflict with Generic Secret Path Name in ~/.secrets.json #74

Open Jalalx opened 1 month ago

Jalalx commented 1 month ago

The current secret path defined in the Harness CLI uses a very generic file name (~/.secrets.json), which has a potential risk of conflicting with other tools (or personal notes) that might use the same file name.

const SECRETS_STORE_PATH = ".secrets.json"

Is there a specific reason for choosing such a generic name for this file?

To reduce the risk of conflicts, it would be beneficial to store this file in a dedicated directory, such as ~/.harness/.secrets.json.

Jalalx commented 1 month ago

Seems to be duplicate of https://github.com/harness/harness-cli/issues/37