config: merge all prod config back into a single file (bug 2024547)#85
Open
config: merge all prod config back into a single file (bug 2024547)#85
Conversation
Workload selection is now done via the `PULSE_ROUTING_KEY` set in the environment of each deployment. We retain the -firefox and -thunderbird configuration files as noop for now, so as no to create unexpected failures with current deployments that may still be looking for them.
dklawren
approved these changes
Mar 20, 2026
dklawren
left a comment
There was a problem hiding this comment.
LGTM but might be best if one of the reviewers approves this as well.
cgsheeh
approved these changes
Mar 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Workload selection is now done via the
PULSE_ROUTING_KEYset in the environment of each deployment.We retain the -firefox and -thunderbird configuration files as noop for now. This is to avoid unexpected failures with current deployments that may still be looking for them. They also update the routing key, to match what future environments should set for
PULSE_ROUTING_KEY(see https://github.com/mozilla/webservices-infra/pull/10205), so that workers started with those configurations don't mistakenly grab messages that should have been processed by others.