Harness secrets

Export secrets into a Harness project.

The connection

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

Direction	What it does
`export`	Writes names and values from penv into the store.

Harness returns no value once it holds one, so penv 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.

You paste a credential you already hold. penv seals it and never shows it again.

Field	Label	Kind	Required	What it is
`apiKey`	API key	secret, masked here and sealed	yes	A Harness API key with secret create and edit permissions.

Fixed when you connect, and shared by every mapping on it.

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

Answered 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.

penv probes for these when it verifies 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.