- read allowed emails from config instead of env(), which returns null once configs are cached in production
- allow the root user by id instead of matching their email
- clean up gate code
On cloud, DeploymentException and TimeoutExceededException are expected
failure modes that pollute the Horizon failed jobs UI. Listen to JobFailed
events and scrub the entry via JobRepository::deleteFailed so operators
are not alerted for noise failures. Self-hosted instances are unaffected.
Add HORIZON_ALLOWED_EMAILS env var to grant additional users access to
the Horizon dashboard. Root user (User ID 0) always retains access.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
- Removed the private property for application deployment queue ID in ApplicationDeploymentJob and utilized constructor property promotion.
- Added a tags method in ApplicationDeploymentJob to properly identify the worker running the job.
- Updated HorizonServiceProvider to handle cases where the deployment queue ID is blank, preventing potential errors during job processing.
- Cleaned up the isAnyDeploymentInprogress function by removing unnecessary whitespace.
- Updated HorizonServiceProvider to extend from HorizonApplicationServiceProvider for improved functionality.
- Added a call to the parent boot method to ensure proper initialization.
- Cleaned up the gate method by removing unnecessary whitespace.
