-
Notifications
You must be signed in to change notification settings - Fork 24
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
Ability to provide path to get the ops files from #29
base: main
Are you sure you want to change the base?
Conversation
…ady run processes.
That's all the commits. I'm sorry for the mess of submitting multiple commits to this pull request after it was originally raised. This is the first time I'm working on a pull request. I've tested all possible scenarios I could think off and it works fine now. Enhancements so far:
|
…den while running `operations:process` command. This is useful, say in case you wish to implement operations for a multi-tenancy setup using `spatie/laravel-multitenancy`. Most multi-tenancy packages require you to implement a special interface for jobs so that they can be tagged as a tenant job. This change provides support for that so that the developer can extend the `OneTimeOperationProcessJob` job and add a the required implementation of the TenantAware (or similar) interface so that the jobs run in tenancy.
Support for |
…er to resolve the job class.
This enhancement provides an extra parameter to the
operations:show
andoperations:process
commands to allow user to specify the path the operations files can be loaded from.