Harness secrets

Export secrets into a Harness project.

Connection

What	This provider
Vendor	Harness
Key	`harness-secrets`
Availability	`available`. You can connect it today.
Credential we hold	`harness-key`
Values read back	no
Activation	`immediate`

Direction	What it does
`export`	We write names and values from your environment into the store.

Harness returns no value once it holds one, so we can write here and cannot read back.

immediate. The running app sees a new value at once.

Direction	Policies you can pick
`export`	`create_only`, `overwrite`, `overwrite_and_prune`

How syncs work says what each one does.

Paste a credential from the vendor. We seal it and never show it again.

Field	Label	Kind	Required	What it is
`apiKey`	API key	secret; we mask it here and seal it	yes	A Harness API key with secret create and edit permissions.

You set these when you connect. Every mapping on the connection shares them.

Field	Label	Kind	Required	Advanced	What it is
`accountIdentifier`	Account identifier	text	yes	no	The accountIdentifier segment of your Harness URL.

You answer these once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`orgIdentifier`	Organization	text	yes	no	The organization holding the project.
`projectIdentifier`	Project	text	yes	no	Secrets land at this project's scope, beside the ones it already holds.

We probe for these when we verify the connection.

Permission	Directions	Blocking	Without it
`core_secret_view`	every direction	yes	Preview cannot list the project's secrets.
`core_secret_edit`	`export`	yes	Export cannot write anything.