Execution config
Choose how configuration values are passed to your connector at runtime and how long a single run can take.
The Execution configuration step sets how configuration values reach your connector at runtime and how long a single run can take.
Execution mode
The Execution configuration step shows the execution mode selected when the connector was created. The execution mode determines how individual configuration values, authentication credentials, and secrets are passed to your connector at runtime.
The execution mode is set at creation and cannot be changed afterward. If you need a different mode, create a new connector.
Environment variable (recommended)
Individual config values are passed as uppercase environment variables. Dashes in the command option are replaced with underscores.
API_KEY=abc123 BASE_URL=https://api.example.com php ./bin/console connector:run:importAuthentication credentials use the PUP_AUTH_ prefix. Secrets are passed as a JSON string in REGISTERED_SECRETS.
This mode works with any language and framework — just read environment variables.
Command options
Individual config values are appended as --flag=value CLI arguments.
php ./bin/console connector:run:import --api-key='abc123' --base-url='https://api.example.com'Authentication credentials use the --pup-auth- prefix. Secrets are passed via --registered-secrets.
Use this mode if your CLI framework expects flags rather than environment variables.
Run timeout tier
The Connector run timeout tier sets the time limit for a single run of your connector: the maximum time a run can take before it is stopped. You set it per connector version and choose one of three options:
- Short (6h)
- Standard (24h) — the default
- Long (70h)
A shorter tier stops a stuck run sooner, so pick the shortest tier that still covers your connector's longest expected run. You can change the run timeout tier at any time.
How is this guide?