Environment Secrets Store

Fetch secrets from environmental variables.

The Environment Secrets Store block is a secure and flexible solution for fetching secrets stored as environmental variables.

How This Block Works

It is designed to enable Workflows to access sensitive information, such as API keys or service credentials, without embedding them directly into the Workflow definitions.

This block simplifies the integration of external services while prioritizing security and adaptability. You can use secrets fetched from environment (which can be set by system administrator to be available in self-hosted inference server) to pass as inputs to other steps.

Credentials security

It is strongly advised to use secrets providers (available when running self-hosted inference server) or workflows parameters to pass credentials. Do not hardcode secrets in Workflows definitions.

Blocks limitations

This block can only run on self-hosted inference server, we Roboflow does not allow exporting env variables from Hosted Platform due to security concerns.

🛠️ Block configuration

Block has configuration parameter variables_storing_secrets that must be filled with list of environmental variables which will be exposed as block outputs. Thanks to that, you can use them as inputs for other blocks. Please note that names of outputs will be lowercased. For example, the following settings:

variables_storing_secrets=["MY_SECRET_A", "MY_SECRET_B"]

will generate the following outputs:

• my_secret_a

• my_secret_b

Type identifier

Use the following identifier in step "type" field: roboflow_core/environment_secrets_store@v1 to add the block as a step in your workflow.

Properties

Name	Type	Description	Refs
name	str	Enter a unique identifier for this step..	❌
variables_storing_secrets	List[str]	List with names of environment variables to fetch. Each will create separate block output..	❌

The Refs column marks possibility to parametrise the property with dynamic values available in workflow runtime. See Bindings for more info.

Input and Output Bindings

The available connections depend on its binding kinds. Check what binding kinds Environment Secrets Store in version v1 has.

Input and output bindings

• input

• output

  • * (*): Equivalent of any element.

Example JSON definition

{
	    "name": "<your_step_name_here>",
	    "type": "roboflow_core/environment_secrets_store@v1",
	    "variables_storing_secrets": [
	        "MY_API_KEY",
	        "OTHER_API_KEY"
	    ]
	}