Andrii Kasian
Andrii Kasian
Use plugin instead of events. For example if you intercept ResourceModel::save method you can access to object->getId() method to know is it create or update event.
@ilnytskyi Can you provide example of configuration that does not work for you. I believe that if you add base configuration to your area configuration, all should work as expected....
Also will be good to split to two RFC. One about engine level ability. And one about user space registration.
For me it is looks like a bug
Please try use 2.1-develop branch of sample data for 2.1.7 Magento version
@hostep Are you sure that this issue is not reproducible on version < 2.4.7? My assumption that this issue caused by switching from http1 to http2 that allow up to...
You probably can archive the same by plugin on `$schedule->save()` method
I believe it's suboptimal to update this command with db unrelated stuff. As an alternative you can introduce new `setup::amgp:status`command