Version Specification¶

Navigate versions with Git-like syntax.

AWS SSM Parameter Store¶

Note

SSM Parameter Store uses numeric version numbers (1, 2, 3, ...) that auto-increment on each update.

<name>[#VERSION][~SHIFT]*
where ~SHIFT = ~ | ~N  (repeatable, cumulative)

Syntax	Description
`/my/param`	Latest version
`/my/param#3`	Version 3
`/my/param~1`	1 version ago
`/my/param#5~2`	Version 5 minus 2 = Version 3
`/my/param~~`	2 versions ago (`~1~1`)

AWS Secrets Manager¶

Note

Secrets Manager uses UUID version IDs and staging labels instead of numeric versions. AWSCURRENT and AWSPREVIOUS are special labels automatically managed by AWS—AWSCURRENT always points to the latest version.

<name>[#VERSION | :LABEL][~SHIFT]*
where ~SHIFT = ~ | ~N  (repeatable, cumulative)

Syntax	Description
`my-secret`	Current (AWSCURRENT)
`my-secret:AWSPREVIOUS`	Previous staging label
`my-secret#abc123`	Specific version ID
`my-secret~1`	1 version ago

Important

When specifying version-only syntax like '#3' or ':AWSPREVIOUS', you must use quotes to prevent shell interpretation of the # (comment) or : characters.

Tip

~ without a number means ~1. You can chain them: ~~ = ~1~1 = ~2

Google Cloud Secret Manager¶

Note

Google Cloud Secret Manager uses integer version numbers (1, 2, 3, ...) plus the latest alias. There are no staging labels, so :LABEL syntax does not apply.

Syntax	Description
`my-secret`	Latest version
`my-secret#3`	Version 3
`my-secret~1`	1 version ago

Azure Key Vault¶

Note

Azure Key Vault versions are opaque version IDs. There are no staging labels, so :LABEL syntax does not apply.

Syntax	Description
`my-secret`	Current version
`my-secret#<id>`	Specific version ID
`my-secret~1`	1 version ago

Azure App Configuration¶

Note

Azure App Configuration is unversioned. #, ~, and : are valid key characters — the whole argument is the literal key name, not a version spec — and log reports that history is unsupported.