envfly list
List all environments and their variables in your EnvFly project.Usage
Description
Thelist
command displays all environments in your project along with their variables. This is useful for:
- Overview: Get a quick overview of all environments
- Audit: Review what variables are stored in each environment
- Debugging: Check if variables are properly stored
- Documentation: Generate documentation of your environment structure
Options
--environment, -e
--environment, -e
Type:
string
List variables for a specific environment only. bash envfly list --environment production envfly list -e development
--format, -f
--format, -f
Type:
string
(json, yaml, table) Default: table
Output format
for the list. bash envfly list --format json envfly list -f yaml envfly list --format table
--show-values, -v
--show-values, -v
Type:
boolean
Default: false
Show actual variable values (use
with caution). bash envfly list --show-values envfly list -v
--filter, -F
--filter, -F
Type:
string
Filter variables by name pattern. bash envfly list --filter "DB_*" envfly list -F "API_*"
--sort, -s
--sort, -s
Type:
string
(name, environment, updated) Default: environment
Sort order for the output. bash envfly list --sort name envfly list -s updated
Examples
Basic List
List Specific Environment
JSON Output
Filter Variables
Show Values (Use with Caution)
Use Cases
Integration Examples
CI/CD Pipeline
Scripting
Team Collaboration
Error Handling
No Environments Found
No Environments Found
Error:
No environments found in this project
Solution: Initialize
the project first: bash envfly init envfly push development DATABASE_URL="your-db-url"
Environment Not Found
Environment Not Found
Error:
Environment 'production' not found
Solution: Check
available environments: bash envfly list
Permission Denied
Permission Denied
Error:
Permission denied: Cannot access environment 'production'
Solution: Check your team permissions or contact your admin.Best Practices
Regular Audits
Regular Audits
- Run
envfly list
regularly to audit your environments - Use JSON format for automated processing - Filter sensitive variables for security reviews
Team Communication
Team Communication
- Share environment structure with new team members - Document variable naming conventions - Use consistent environment names across projects
Automation
Automation
- Integrate listing into CI/CD pipelines - Generate automated reports - Use for compliance and audit purposes