Reference
Northflank global secrets
Secrets every project in a Northflank team inherits, merged per key.
Secrets every project in a Northflank team inherits, merged per key.
The connection
| What | This provider |
|---|---|
| Vendor | Northflank |
| Key | northflank-global-secret |
| Availability | available. You can connect it today. |
| Credential penv holds | northflank-token |
| Values read back | no |
| Activation | restart-on-write |
What it moves
| Direction | What it does |
|---|---|
export | Writes names and values from penv into the store. |
Northflank returns no value once it holds one, so penv can write here and cannot read back.
When a written value goes live
restart-on-write. Writing a value restarts the workload.
What happens to a name that exists
| Direction | Policies you can pick |
|---|---|
export | create_only, overwrite, overwrite_and_prune |
How syncs work says what each one does.
How you connect
You paste a credential you already hold. penv seals it and never shows it again.
| Field | Label | Kind | Required | What it is |
|---|---|---|---|---|
token | API token | secret, masked here and sealed | yes | An API token with project:read, plus secret:write to export. |
What a mapping asks for
Answered once per environment you map.
| Field | Label | Kind | Required | Advanced | What it is |
|---|---|---|---|---|---|
secretId | Global secret | text | yes | no | The global secret this environment maps onto. Its URL ends with the id. |
Permissions it needs
penv probes for these when it verifies the connection.
| Permission | Directions | Blocking | Without it |
|---|---|---|---|
project:read | every direction | yes | penv-cloud cannot confirm the token reaches this team. |
secret:write | export | yes | Export cannot write anything. |