Closed Bug 1301380 Opened 9 years ago Closed 9 years ago

Make ROUTING_KEYS configurable

Categories

(Release Engineering :: Release Automation, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jlorenzo, Assigned: csheehan)

References

Details

Attachments

(1 file)

release-automation-notifications@m.c got emails from the staging release pipeline[1]. Rail pointed out that pulse-notify listens to a given set of TaskClusters routes, no matter if we're in prod or staging[2]. Let's make [2] configurable via an env var. [1] For instance: https://groups.google.com/a/mozilla.com/forum/?utm_medium=email&utm_source=footer#!msg/release-automation-notifications/JHysVVa-IK4/riY3HgjIAQAJ [2] https://github.com/mozilla-releng/pulse-notify/blob/8b2a51e77b29965ab1cb2deac8557c79ca8b72f2/pulsenotify/consumer.py#L27
Assignee: nobody → csheehan
Blocks: 1300754
Blocks: 1256998
Comment on attachment 8789537 [details] [review] Moves source of ROUTING_KEYS to 'ROUTING_KEYS' env var LGTM. Before merging these, we should add the corresponding routes to the heroku apps.
Attachment #8789537 - Flags: review?(rail) → review+
These routes have been added: * to production instance => route.index.releases.v1.mozilla-beta.#:route.index.releases.v1.mozilla-esr45.#:route.index.releases.v1.mozilla-release.# * to dev instance => route.index.releases.v1.jamun.# In order to test the dev instance, I plugged heroku to mozilla-releng/pulse-notify#master. Please, let me know if I should wire it back to cgsheeh/pulse-notify#master. I think we're ready to merge in master and in production.
(In reply to Johan Lorenzo [:jlorenzo] from comment #3) > I think we're ready to merge in master and in production. Sweet. Let's do it! On it.
This is should be done now. * adjusted the dev pulse credentials and queue name to be under the same account * killed the queues using pulseguardian (otherwise they won't unbind the old routing keys) * restarted the prod dyno and started the dev dyno to make sure the queues are recreated with the new routing keys. * verified the list of keys in pulseguardian - all look good! Thank you Connor!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
I just started a release in ship-it-dev. I confirm the notifications are now sent to release-automation-notifications-dev only[1]. Thank you Connor :) [1] https://groups.google.com/a/mozilla.com/forum/?utm_medium=email&utm_source=footer#!msg/release-automation-notifications-dev/OFHdKcYBuYY/bj8CN9fXAQAJ
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: