[11.x] Add environmentSchedule method to the Scheduling Event #51126
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces the ability to set different schedules for a job based on the environment.
Scenario:
You have a site in production and a dev site where you are making calls to a 3rd-party provider. This provider may have API quotas for how often it can be hit so you set different schedules for production and staging.
Current Solution:
Currently, you can use the
->environments()
method to specify which environment to run it in. This works great but also leads to duplicate code.The Solution:
I'd like to introduce the
environmentSchedule
method to simplify the schedulingThis reduces code duplication by simply accounting for both schedules in the same definition. I am passing in the current environment to the callback but users could use whatever they like.