Env Providers Bundle Laravel Package

Product Decisions This Supports

• Feature Expansion: Enables parsing .env variables into structured PHP arrays (e.g., comma-separated lists → native arrays), reducing manual parsing logic in Symfony 3+ applications.
• Roadmap Alignment: Accelerates adoption of Symfony’s .env system by mitigating frustrations with its rigid dotenv format, aligning with a shift toward environment-driven configuration.
• Build vs. Buy: Avoids reinventing wheel for array parsing from strings; leverages lightweight, open-source solution (Apache-2.0) instead of custom development.
• Use Cases:
  • Multi-value configurations: E.g., ALLOWED_ROLES=admin,user,guest → ['admin', 'user', 'guest'] for ACLs.
  • Legacy migration: Gradually transition from parameters.yml to .env while preserving array syntax.
  • DevOps/Infrastructure: Simplify CI/CD pipelines by reducing need for pre-processing scripts.

When to Consider This Package

• Adopt if:
  • Your Symfony 3+ app relies on .env files for configuration but lacks native support for array parsing.
  • You frequently handle comma-separated lists (e.g., flags, enums, collections) in environment variables.
  • Your team prefers declarative config over imperative parsing logic in PHP.
• Look elsewhere if:
  • You’re using Symfony 5+ (native env() function supports arrays via %env(array:VAR)%).
  • Your use case requires complex transformations (e.g., nested arrays, JSON parsing)—consider a custom provider or Symfony’s env() extensions.
  • You prioritize bundle maturity/stars over functionality (this package is untested in production).

How to Pitch It (Stakeholders)

For Executives: "This bundle lets us use .env files like parameters.yml—turning strings like FEATURE_FLAGS=analytics,notifications into usable PHP arrays with zero code changes. It’s a 5-minute install that saves dev time and reduces config errors, especially for teams migrating from legacy systems."

For Engineers: *"Symfony’s dotenv is limited for arrays, but this bundle adds %env(array:VAR)% support. Perfect for:

• Quick wins: Replace explode() calls in config with declarative .env parsing.
• Consistency: Standardize how we handle lists (e.g., database hosts, feature toggles) across environments.
• Future-proofing: Works today, aligns with Symfony’s direction, and avoids vendor lock-in. Tradeoff: Minimal adoption risk (lightweight, Apache-licensed), but test in staging first—it’s a new package."*