Created attachment 8717498[details][diff][review]
updates_release_promotion-gecko-dev.diff
Just wanted to make sure that I'm not in a wrong direction. :)
The idea is to use the same (or almost) tools to bump configs, tag (still need this for update verification) and push the top blob info to balrog. Also avoid 2 builders for RC that sometimes give us troubles racing each other.
Instead of using rule IDs I use aliases (I hope it works without any changes).

Comment on attachment 8717499[details][diff][review]
updates_release_promotion-tools.diff
Review of attachment 8717499[details][diff][review]:
-----------------------------------------------------------------
I'm not a huge fan of duplicating the two scripts, but I can live with it if you find a better name for them. These will end up being the only ones that exist after we fully switch to release promotion, so please choose a name that makes sense for that world.
::: release/update-verify-bump.pl
@@ -1,1 @@
> -#!/usr/bin/perl -w
Yay, script death!
::: scripts/updates/balrog-release-pusher-rp.py
@@ +25,5 @@
> + parser.add_argument(
> + "--username", required=True, help="Username in the credentials file")
> + parser.add_argument(
> + "--channel", dest="channels", action="append", required=True,
> + help="Release blob channels")
This is not a very useful help message. How about something like "Channels to set-up fileUrls for"?
@@ +28,5 @@
> + "--channel", dest="channels", action="append", required=True,
> + help="Release blob channels")
> + parser.add_argument(
> + "--test-rule", dest="test_rules", action="append", required=True,
> + help="Test channels that will be automatically enabled")
Please change the name of this to match whatever is used in the mozharness config.