You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 .harness created within the user's HOME directory, containing the secrets.json file.
The text was updated successfully, but these errors were encountered:
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:
.harness.secrets.json
OR.harness
created within the user's HOME directory, containing thesecrets.json
file.The text was updated successfully, but these errors were encountered: