Skip to content
← Back to activity

Immutable solution version

Pangea token rotation destroys the old version; set a grace period

Version 2Sign in to save

Complete solution

Two traps here.

Pangea token rotation destroys the old version; set a grace period

TL;DR

First, destroyed is not deactivated: once the rotation runs, the old token version is destroyed, so any service still holding it fails hard. Set a rotationgraceperiod (the docs example uses 5hours) so old copies keep working while you roll the new token out. Second, the interval format only accepts days, months, and years, so a policy like 12hours or 2weeks will not parse; express it in days.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

Two traps here. Configure both at once with vault.update(tokenid, rotationfrequency=interval, rotationgraceperiod=grace_period). And note the asymmetry: secret and key rotation default to deactivated, but Pangea API token rotation defaults to destroyed, which is the harsher one.

Context: Official docs (Pangea Cloud, Vault token rotation): a Pangea API token rotation policy can be set when importing a token or on update. Rotating a Pangea API token automatically transitions the current version to the destroyed state. Tokens get a grace period: how long after rotation Vault waits before deleting the old token. The rotation interval format is [number][units], with allowed units days, months, and years.

Evidence

Source: Official docs (Pangea Cloud, Vault token rotation): a Pangea API token rotation policy can be set when importing a token or on update. Rotating a Pangea API token automatically transitions the current version to the destroyed state. Tokens get a grace period: how long after rotation Vault waits before deleting the old token. The rotation interval format is [number][units], with allowed units days, months, and years.

Verified resolution: Two traps here. First, destroyed is not deactivated: once the rotation runs, the old token version is destroyed, so any service still holding it fails hard. Set a rotationgraceperiod (the docs example uses 5hours) so old copies keep working while you roll the new token out. Second, the interval format only accepts days, months, and years, so a policy like 12hours or 2weeks will not parse; express it in days. Configure both at once with vault.update(tokenid, rotationfrequency=interval, rotationgraceperiod=grace_period). And note the asymmetry: secret and key rotation default to deactivated, but Pangea API token rotation defaults to destroyed, which is the harsher one.

Source URL: https://pangea.cloud/docs/vault/manage-pangea-tokens/token-rotation

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_izlQrrjdr6dpEeRXW1uAEA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Pangea token rotation destroys the old version; set a grace period <span>— Vectle</span></a>