Disable Bundle Laravel Package

Product Decisions This Supports

• Feature Flagging & A/B Testing: Enables dynamic disabling of controllers/actions without code changes, useful for gradual rollouts or feature toggles.
• Maintenance Mode: Quickly disable entire controllers or actions during deployments, migrations, or outages (e.g., @Disable(until="2024-12-31")).
• Conditional Redirects: Route users to alternative pages (e.g., maintenance pages) or APIs during downtime without hardcoding logic.
• Legacy System Sunset: Phase out deprecated endpoints by disabling them incrementally via annotations (e.g., @Disable(after="2024-06-01")).
• Build vs. Buy: Avoid reinventing annotation-based feature toggles for Symfony; leverage existing, albeit dated, infrastructure.
• Roadmap: Prioritize if your team uses Symfony 2.x and needs lightweight, annotation-driven control over endpoints.

When to Consider This Package

• Avoid if:
  • Using Symfony 3+ or 4+: Incompatible (last release 2013); modern alternatives (e.g., Symfony’s ExpressionLanguage or Mercure) exist.
  • Need active maintenance: No updates in 10+ years; security/bug fixes unlikely.
  • Require complex scheduling: Limited to basic date/time ranges (no cron-like triggers or external API hooks).
  • Prefer database-backed toggles: This is annotation-only; no dynamic config via DB or Redis.
  • Using non-Symfony frameworks: Not applicable to Laravel, Silex, or custom PHP apps.
• Look elsewhere if:
  • Need feature flags with analytics (e.g., LaunchDarkly, Flagsmith).
  • Want role/permission-based disabling (e.g., @Disable(roles="ROLE_ADMIN")).
  • Require multi-environment support (e.g., disable in staging but not prod).

How to Pitch It (Stakeholders)

For Executives: "This package lets us toggle entire API endpoints or pages on/off with a single annotation—no code deployments needed. For example, we could disable a beta feature for 10% of users during a test, or automatically redirect customers to a maintenance page during a database migration. It’s a low-risk way to add flexibility to our Symfony 2.x app without heavy engineering lift."

For Engineers: "If we’re stuck on Symfony 2.x and need a lightweight way to disable controllers/actions by date/time (e.g., for deployments or sunsetting features), this bundle provides annotation-based toggles with optional redirects. Tradeoff: It’s unmaintained (last update 2013), so we’d need to vet it for security/compatibility. For new projects, modern alternatives like Symfony’s ExpressionLanguage or third-party flag services would be better."