Fix a variable that does not resolve
A variable that reads its value from a secret can stop getting one, for example when the secret is deleted. Jaah then leaves the variable out of every new slot, and the project's code runs without it. The variables list marks such a row with !, and the variable's page shows Not resolved. This page finds the cause and fixes it.
Who can do this: a variable that applies to Everyone needs the permission to edit the project. An Only me variable can be fixed only by the member it belongs to.
Fix it
-
In the sidebar, select Directory, then the Projects tab.
-
Select the project's name to open its settings, then select Variables in its list of sections.
-
Find the row marked !. The reason is written under its name, starting Not resolved —.
-
Select the variable's name. Its page opens beside the list with the same line above the fields, starting ⚠ Not resolved —.
-
Match the line to its fix:
The line says Fix the credential this variable referenced was deleted Pick another secret in Credential, then its Credential field. Or set Value from to A literal for a value that isn't secret. you have no grant on credential, or the identity this variable resolves under has no grant Pick a secret in Credential that the list offers: it shows only the ones you may use. Who may use a secret is set by its owner, see How secrets work. field … is not set on credential Fill that field on the secret (see Replace or delete a secret), or pick a field that has a value in Credential field. NodeVault: Jaah's servers can't open Jaah can't read a NodeVault secret to write it into a variable. Pick a secret without NodeVault, or attach the secret to the project so tasks fetch it on the node. -
Picking another Credential clears Credential field, so pick the field again.
-
Select Save. Saved. shows beside it once the change is stored.
-
Check the page: the Not resolved chip and the ⚠ line are gone. Back on the list, the row's mark is ✓ or –.
-
Select Show preview. Under What your slot gets, the variable's line is there and no longer commented out.
Fixing a secret on its own page, such as filling a missing field, fixes every variable that reads it: no Save is needed on the variable. A slot already in use keeps what it was given; the next slot a task claims gets the value.
Related
- Change or delete an environment variable: change a variable's name, value or description, or remove it.
- Add an environment variable: give a project's tasks a typed value, a secret's field or a port.
- Project variable: every field and status line on a variable's page.