Update to Autogenerated Lists in LDAP

RESOLVED FIXED

Status

RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: jen, Unassigned)

Tracking

Details

(Reporter)

Description

4 years ago
1)  Li-lunch automated list has been retired and can be deleted
2)  release@mozilla.com is currently an automated list that they want to convert to a user managed list.  Can we coordinate removing it from LDAP and adding it to the Gads exception list?
(Reporter)

Comment 1

4 years ago
3)  Jonath-lunch is an automated list that has also been retired and can be deleted

Comment 2

4 years ago
if the release@ list is user-managed, then we don't need it on the exception list, right? probably just delete the existing admin-managed list and let someone create a new Google Group that is user generated?
I've removed the crons for johnath-lunch and li-lunch
Committed revision 98761.

Comment 4

4 years ago
I removed li-lunch and jonath-lunch from LDAP, the next GADS run should wipe them from google. We need to proceed carefully with the release@ list so that we create the new user list about the same time as deleting the admin-created list.
Removed the scripts from scripts.pp
Removed the scripts from the dev/stage/prod hosts

Committed revision 98762.
(In reply to Justin Dow [:jabba] from comment #4)
> I removed li-lunch and jonath-lunch from LDAP, the next GADS run should wipe
> them from google. We need to proceed carefully with the release@ list so
> that we create the new user list about the same time as deleting the
> admin-created list.

:jabba - we may be okay here -- the list already is visible and manageable via google groups, however our changes there keep getting overwritten by the auto update.

The intent is to leave this as a private google group, not convert to a mailman list.

Does that make sense?
Flags: needinfo?(jdow)

Comment 7

4 years ago
I think what I'm suggesting is deleting the existing group and re-creating it using the google groups interface. This way gads will automatically ignore it and we don't need to maintain an exclusion rule for it. As it is now, it is considered an "admin-created group" that has been delegated to users to manage, so gads will try to manage it.
Flags: needinfo?(jdow)
Okay, I'm not following, but y'all are the experts. Here's our business needs:
- maintain the existing release@m.c address (with support for plus-addresses)
- not loose any mail (minor delays <30m are fine with notice).

If we can't guarantee no loss of email, then we'll need to schedule the cutover time to be not during a critical period. (This week and next are critical for FF 35 activities. At the extreme, there is a TCW on Jan 24.)

We have lots of key emails auto-generated to this address that inform us and other teams of progress of release builds.

Will what you propose in comment 7 meet our needs?
Flags: needinfo?(jdow)
(Reporter)

Comment 9

4 years ago
Hi Jabba:  Let me know when you delete the list out of LDAP.  I'll go ahead and create the list and make Hal the owner.   I'll work with him to get it all repopulated.

Jen
(Reporter)

Comment 10

4 years ago
Per update on service now ticket - these are the owners of the list when we recreate it in Google.

 coop@m.c 
 catlee@m.c
 hwine@m.c
(Reporter)

Updated

4 years ago
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED

Updated

4 years ago
Flags: needinfo?(jdow)
You need to log in before you can comment on or make changes to this bug.