Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to selectively enable/disable #58

Open
tacman opened this issue Jan 16, 2024 · 2 comments
Open

Add ability to selectively enable/disable #58

tacman opened this issue Jan 16, 2024 · 2 comments

Comments

@tacman
Copy link
Contributor

tacman commented Jan 16, 2024

I'd like to only enable the monitor in certain situations, but want to keep it in bundles.php (so routing and dependency injection works, even if not enabled).

it looks like there's only the ability to disable live-components

zenstruck_messenger_monitor:
    live_components:
        enabled: false
        role: ROLE_MESSENGER_MONITOR
@kbond
Copy link
Member

kbond commented Feb 15, 2024

Good idea, keep 'em coming!

Little update on this bundle: it has taken a bit of a backseat right now while I focus on other things but I really want to get back to developing this. I've chatted with @nikophil (he helps me maintain other zenstruck packages) and he's going to help me development here as well.

@tacman
Copy link
Contributor Author

tacman commented Jul 17, 2024

I see v0.3 was released last week, and I think the ability to disable monitoring via a stamp or attribute is new, yes?

I'm still running into issues where the monitoring via this bundle appears to hang the message processing, so the ability to completely disable the bundle from the config is important. Otherwise, to disable the bundle I have to remove the ProcessedMessage entity and repository, and the config, and of course from bundles.php.

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

No branches or pull requests

2 participants