Improve the amount of RTV's provided

[0xdeafcafe]

Add support for more Realtime Values OOTB.

• UUID
• Date
• Time
• Datetime (with delta)
• SHA Digests (SHA1, 256, 512, etc)
• Base64 encode (with websafe version)
• Base64 encode w/o padding
• Base64 decode with websafe version + no padding
• URL encode/decode
• File binary data
• Special characters (\n, \t)
• Add delta option to timestamp
• Add options to Nonce (length?)
• Request Parent Folder Name
• Request Name
• Request Method
• Request Header
• Response Status Code
• Response Header
• Response Body Text
• Response Body JSON (XPath)

[billinghamj]

Timestamps in more formats - e.g. ISO8601 dates (rather than date-times), with custom formats, and perhaps with duration adjustments/offsets (e.g. -P1D)

[billinghamj]

Timestamp format conversion(?)

[billinghamj]

JS map snippet perhaps - input + small arrow function

[billinghamj]

HMAC digests - input + key from another variable

On all digests, probably need to be able to choose between hex and binary/raw, or allow any of the encoding variable options to be chosen

On B64, probably worth unpadded options too

[billinghamj]

KSUIDs would be quite case-specific, but still nice to have

[billinghamj]

Perhaps URL search params - so like URL encode, but embedding a whole table within one value - would be good for things like SSO parameters

Along with that, potentially being able to refer to another value in the same scope - e.g. to generate a signature for your SSO param

[billinghamj]

The name of the current request

The name of the folder the current request is in

Variable lookup by item name, allowing variables in that input

Would allow for making the URL automatically match the folder + request name:

e.g.: {{ var 'base_url_{{ current_folder_name }}' }}/latest/{{ current_request_name }}