Secret rerolls
Reassign an output reference when the upstream resource changes.
You set up an output reference pointing your Postgres plugin at a DigitalOcean managed database. A month later you migrate to Neon. You do not have to delete and recreate the Postgres account — you can reroll the secret.
What “reroll” means
A reroll reassigns a field that was pointing at one output to point at a different output (or to a literal value). Infrawrench keeps a per-field state record, so rerolling one field does not touch the rest of the resource.
How to reroll
- Open the resource that has the referenced field.
- Find the field (for example Connection string). A field holding a secret or a reference shows
•••••, orfrom: <source resource>when it currently points at an output, with a small Reroll link beside it. Some plugins label the link for the field instead — the Postgres account calls it Reroll Connection. - Click Reroll. A Reroll
<field>dialog opens with two tabs: From resource and Paste literal value. - Pick the new upstream resource, or switch to the second tab and paste a literal value.
- Click Confirm.
Infrawrench will resolve the new source on the next connection. Existing connections are not forcibly dropped.
Common reroll scenarios
- Provider migration — Postgres database moves from DO to Neon.
- Rotated credentials — you revoked the upstream token and issued a new one under a different resource.
- Environment split — staging and prod were sharing one database; you split them and want the prod client to point at a different upstream.
Reroll vs edit
If the upstream resource itself changed (e.g. DO rotated the password), you do not need to reroll — the output reference re-resolves automatically. Reroll is only for switching which upstream you point at.