Reference
Northflank
Sync a penv environment into a Northflank project secret group.
Sync a penv environment into a Northflank project secret group.
The connection
| What | This provider |
|---|---|
| Vendor | Northflank |
| Key | northflank-project-secret |
| Availability | available. You can connect it today. |
| Credential penv holds | northflank-token |
| Values read back | yes |
| Activation | restart-on-write |
What it moves
| Direction | What it does |
|---|---|
import | Reads names and values out of the store into penv. |
export | Writes names and values from penv into the store. |
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 |
|---|---|
import | skip_existing, new_version, fail |
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 and secret: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 |
|---|---|---|---|---|---|
projectId | Project | text | yes | no | The ID in your Northflank project URL. |
secretGroupId | Secret group | text | yes | no | Give penv-cloud a group of its own. A concurrent edit here can be overwritten. |
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 see the project at all. |
secret:read | import | yes | Import cannot read values. |
secret:write | export | yes | Export cannot write anything. |