Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFE] Change Secrets File Name #37

Open
Ompragash opened this issue Aug 21, 2023 · 0 comments
Open

[RFE] Change Secrets File Name #37

Ompragash opened this issue Aug 21, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@Ompragash
Copy link
Collaborator

Presently, the API token for Harness is saved in a file called .secrets.json within the user's HOME directory. The concern with this naming choice is that it lacks distinctiveness, making it challenging to associate it as being related to Harness, similar to secret files for other providers like AWS or Terraform.

For instance, with AWS:
/Users/redacted/.aws/credentials

and for Terraform:
/Users/redacted/.terraform.d/credentials.tfrc.json

Therefore, the suggestion put forth is to house the Harness API token in one of two ways:

  1. Inside a file titled .harness.secrets.json OR
  2. Within a concealed directory named .harness created within the user's HOME directory, containing the secrets.json file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants