Sha256: 6e91a5c8fb29819d5362400e9ce96b4249d606d386971fc606cb541bfb961a02
Contents?: true
Size: 1.21 KB
Versions: 2
Compression:
Stored size: 1.21 KB
Contents
Feature: Key This keyword is an alias of the the `CONTENTS` keyword: ```javascript KEY['vault_id'] ``` Note that: * It should be used specifically when the contents are a Symmetric vault key. * It takes one argument, the name of the vault holding the desired string. * The `KEY` keyword can be used in the **fill_with**, **lock_with** and **unlock_with** fields. Scenario: Close And Open Using with a Key Given the blank contract: """javascript { "header": {}, "vaults": { "random_vault_key":{ "description":"Random Number", "fill_with": "RANDOM_NUMBER", "lock_with": "MASTER_PASSPHRASE", "unlock_with": "MASTER_PASSPHRASE", "contents": "" }, "message":{ "description": "Simple Congratulations Message", "fill_with": "EXTERNAL_DATA", "lock_with": "KEY['random_vault_key']", "unlock_with": "KEY['random_vault_key']", "contents": "" } } } """ When I lock a message in a vault using a symmetric vault key Then I can recover the message using the same key
Version data entries
2 entries across 2 versions & 1 rubygems
Version | Path |
---|---|
vault-tree-0.3.4 | features/keywords/key.feature |
vault-tree-0.3.3 | features/keywords/key.feature |