Secret
Overview
Retrieves a workspace secret for use in a tree
Details
Secrets are intended to protect sensitive information. They are stored encrypted and only accessible to the workspace that owns them.
They are a way of ensuring that:
- Your passwords and sensitive information are kept separate from your Logix, Template and Trigger files.
- Your environments can have different values so you can work against different systems per environment.
⚠️ Secrets are intended to protect sensitive information. However, they can be exposed if you place them in a Data Structure and convert it to a text output such as JSON.
Do so at your own risk.
| Returns |
|---|
| Secret |
Parameters
| Parameter | Parameter | Valid Blocks | Required |
|---|---|---|---|
Use Dynamic Name | Show the Dynamic Name slot in the tree so that it can be set dynamically | Boolean Block Group | No |
Dynamic Name | The dynamic name of this item | Text Block Group | No |
Attributes | Metadata values for this block. Used in XML and multipart/form-data. | Text Block Group | No |
Secret Name | The name of the secret to load | Text Block Group | No |
Is Required | Determines whether or not the parameter is required | Boolean Block Group | No |
Input Parameter Source | Source of the parameter | Text Block Group | No |
Is Null | If true, this block's value will be null | Boolean Block Group | No |