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.json OR
- Within a concealed directory named
.harness created within the user's HOME directory, containing the secrets.json file.
Presently, the API token for Harness is saved in a file called
.secrets.jsonwithin 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/credentialsand for Terraform:
/Users/redacted/.terraform.d/credentials.tfrc.jsonTherefore, the suggestion put forth is to house the Harness API token in one of two ways:
.harness.secrets.jsonOR.harnesscreated within the user's HOME directory, containing thesecrets.jsonfile.