Vault Entry Problem

A message similar to one of the following appears in the Run Variation dialog to alert you:

Order could not be created for recipe-variation.

Validation errors while compiling variation

Vault entry does not exist

Warning

For vault entry changes made to scheduled orders, an error may be difficult to find in the order run logs as the system will resolve a secret to the secret expression rather than the underlying value. In addition, vault values should not be printed to the logs for security reasons.

Visual example in Automation

Details

Vaults remotely store sensitive infrastructure and toolchain credentials as secure, encrypted secrets. Teams can use these secrets as variables to build kitchens and recipes without needing to view the actual values.

For security, users are prevented from running a recipe variation when the order references secrets that are not defined in the global vault or any connected kitchen vault.

Potential causes

A recipe variation will not be executed if the system cannot locate accurate vault information or compile a secret when an order is run.

Solutions

First, check that your recipe variation and kitchen settings only reference secrets contained in connected vaults, then:

• For a missing vault entry, navigate to the Secrets page. Click Add Secret for the global or kitchen secrets list.
• For a misspelled vault entry, navigate to the Secrets page. Click Edit Secret associated with the secret.

Once the vault entry has been fixed, rerun the order.

Best practice is to routinely remove unused or deprecated secrets from your recipe and/or kitchen.

Related topics

Run an Order Vaults and Secrets

Note

Still not working? Contact DataKitchen Support. We can work through this together.