Keystore

formatting...

Tasks sets and gets values from a distributed keystore. This makes is possible to share values between scenarios.

Retreived (get) values are rendered before setting the variable. Stored (set) values are not rendered, so it is possible to store templates.

Step implementations

• Get

• Get default

• Get remove

• Set

• Set text

• Increment default with step

• Decrement default with step

• Pop

• Push

• Push text

• Remove

Statistics

This task only has request statistics entry, of type KEYS, if a key (without default_value) that does not have a value set is retrieved.

Arguments

Name	Type	Description	Default
key	str	name of key in keystore	required
action	Action	literal set or get	required
action_context	str | Any	when action is get it must be a str (variable name), for set any goes (as long as it is json serializable and not None)	required
default_value	Any | None	used when action is get and key does not exist in the keystore	required

Values for set and push operations are not rendered by default, they will be pushed as is. By using argument render, it is possible to change this behaviour, e.g.:

Given value of variable "identification" is "foobar"
Then push "processed" in keystore with value "{{ identification }} | render=True"