Secret Manager Node
Legacy node deprecation (Flow App v5.3.0+)
Starting with Flow App v5.3.0, the legacy Secret Manager node is no longer needed and can be removed from your flows. The Secret Manager plugin fully replaces the node's functionality and operates entirely in the background and. If the system detects a legacy Secret Manager node in your workspace, you will automatically be prompted with a message advising you to delete it.
→ Learn more about the new Secret Manager plugin
Introduction
The Secret Manager node integrates with qibb’s Secret Manager. It automatically fetches secrets and exposes them in the global context, so that they can be accessed in your flow. Note that flows can only fetch secrets of the regarding space they are deployed in.
Secret Manager Node Properties
How to setup secret manager node in your flow
Secrets can be automatically fetched and easily accessed from a flow by using qibb’s Secret Manager node. The Secret Manager can be found in the node catalog. Note that flows can only fetch secrets of the regarding space they are deployed in.
The Secret Manager node offers the following configuration options:
Description | Options | |
|---|---|---|
Autosync | Defines the sync interval, which is fetching the space secrets. |
|
Sync on Save | Toggle if the node should fetch secrets whenever the flow was changed and saved. Note, if your Save Mode is set to “Modified Flows” or “Modified Nodes” the Secret Manager Node may not initiate the sync on save unless it’s properties or position has been changed (blue indicator showing up):  |
|
How to install secret manager node in your flow
Installation
Navigate to your flow app.
Open the Node Catalog in the right sidebar of the editor.
Click on the
(+)button of the Secret Manager node to install it.
Setup
After the installation has been successfully completed, drag and drop the Secret Manager node from the left sidebar into your flow.
Adjust the properties of the node to your needs, such as the Autosync period.
Save your flow.
Avoid dropping multiple instances of this node. Only one instance of this node is required.