HashiCorp Vault

• Secret created or updatedRuns when a secret is created or gets a new version in a key/value engine, in the folder you choose, with its path and version (not its values). Secrets already there when the workflow is turned on don't start it.
• Secret due for rotationRuns once for each secret whose current version is older than the days you choose, such as 90, with its path and age, so it can be changed. Secrets already that old when the workflow is turned on start it too; a new version starts the count again.

• Read secretRead a secret's keys and values, or one key's value such as a password, to use in a later step; the current version or an earlier one. The value is in the step's result for later steps, so anyone who can see this workflow's runs can see it; the run's summary doesn't print it.
• Write secretSave keys and values as a secret, such as an API key from a sign-up or a password changed elsewhere. A secret already at the path gets a new version with exactly these keys; earlier versions are kept.
• Update secret keysSet some keys of a secret, such as a new password, and remove others, keeping the rest as they are. It makes a new version.
• List secretsList the secrets in a folder of a secrets engine, and its folders, or every secret under it. Values aren't read.
• Get secret versionsSee a secret's versions without reading its values: which is current, when each was written, and which are deleted or destroyed, with its custom metadata.
• Delete secretDelete a secret's current version or the versions you name, which 'Restore secret versions' can bring back; or destroy versions, or the whole secret with its history, for good.
• Restore secret versionsBring back deleted versions of a secret, such as one deleted by mistake. Destroyed versions can't be restored.
• Encrypt textEncrypt text with a Transit key, such as a card number or a note to store elsewhere. Only Vault can decrypt it, with the same key.
• Decrypt textDecrypt text that 'Encrypt text' (or anything else using the same Transit key) encrypted; it starts with vault:v. The value is in the step's result for later steps, so anyone who can see this workflow's runs can see it; the run's summary doesn't print it.
• Generate random valueMake a strong random password, or random bytes as hex or base64 for a key, from Vault's own randomness; or a password by one of your Vault's password policies. The value is in the step's result for later steps, so anyone who can see this workflow's runs can see it; the run's summary doesn't print it.
• Check server healthCheck that Vault is up, initialized and unsealed, and whether this server is active or a standby, with its version.
• Look up tokenSee the connection's token: its policies, and when it expires unless renewed. Lodol renews a renewable token as it uses it.

No actions match that.