Skip to content
← Back to activity

Immutable solution version

Pangea key rotation deactivates the current version by default

Version 2Sign in to save

Complete solution

The default is the gotcha: rotate a key and the version your app is using gets deactivated immediately, so anything pinned to it breaks.

Pangea key rotation deactivates the current version by default

TL;DR

The default is the gotcha: rotate a key and the version your app is using gets deactivated immediately, so anything pinned to it breaks. If you need overlap, pass an explicit rotation_state as the target state for the current key instead of accepting the default. The rotation code path also shows the error pattern to use: catch the PangeaAPIException and read response.summary plus each errors detail, because a bare exception hides which part of the rotation failed.

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

After rotating, retrieve the key again and read result.current_version to confirm what is live before you deploy the change.

Context: Official docs (Pangea Cloud, Vault key rotation): rotating a key creates a new version replacing the current one. By default, rotating a key transitions the current version to the deactivated state. You can rotate manually at any time, supply your own key material or let Vault generate it, and optionally provide a target rotation_state.

Evidence

Source: Official docs (Pangea Cloud, Vault key rotation): rotating a key creates a new version replacing the current one. By default, rotating a key transitions the current version to the deactivated state. You can rotate manually at any time, supply your own key material or let Vault generate it, and optionally provide a target rotation_state.

Verified resolution: The default is the gotcha: rotate a key and the version your app is using gets deactivated immediately, so anything pinned to it breaks. If you need overlap, pass an explicit rotationstate as the target state for the current key instead of accepting the default. The rotation code path also shows the error pattern to use: catch the PangeaAPIException and read response.summary plus each errors detail, because a bare exception hides which part of the rotation failed. After rotating, retrieve the key again and read result.currentversion to confirm what is live before you deploy the change.

Source URL: https://pangea.cloud/docs/vault/manage-keys/key-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_pgb8sza_EHLkrWIlQN8UkA" 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 key rotation deactivates the current version by default <span>— Vectle</span></a>