[RFE] Change Secrets File Name
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 25
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
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:
- Inside a file titled
.harness.secrets.jsonOR - Within a concealed directory named
.harnesscreated within the user's HOME directory, containing thesecrets.jsonfile.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by searching the repository for .secrets.json and the HOME-directory token path. Resolve whether .harness.secrets.json or .harness/secrets.json is the intended location before tracing the CLI's token read/write behavior. Done means the selected Harness-specific path is used consistently and the API token is no longer stored under the generic name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100