Skip to content

Conversation

@BowTiedSwan
Copy link

@BowTiedSwan BowTiedSwan commented Dec 30, 2025

When exporting a workflow as code, the .env.example file now includes only the environment variables for integrations actually used in the workflow, instead of all registered plugins.

  • Updated generateEnvExample to accept workflow nodes and extract action IDs.
  • Replaced getAllEnvVars with getEnvVarsForActions to fetch environment variables specific to used integrations.
  • Added getEnvVarsForActions function to retrieve environment variables based on action IDs from the plugin registry.

Fixes #171

- Updated `generateEnvExample` to accept workflow nodes and extract action IDs.
- Replaced `getAllEnvVars` with `getEnvVarsForActions` to fetch environment variables specific to used integrations.
- Added `getEnvVarsForActions` function to retrieve environment variables based on action IDs from the plugin registry.
@vercel
Copy link
Contributor

vercel bot commented Dec 30, 2025

@BowTiedSwan is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

@ctate
Copy link
Collaborator

ctate commented Jan 7, 2026

Appreciate the contribution. Will take a look soon!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Export workflow generates .env.example with all plugin env vars instead of only required ones

2 participants