Closed
Bug 1429354
Opened 6 years ago
Closed 6 years ago
Unable to add new members to Mozilla Heroku account due to 100 member limit
Categories
(mozilla.org :: Heroku: Administration, task)
mozilla.org
Heroku: Administration
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emorley, Unassigned)
Details
Trying to add the another user to the Mozilla Heroku enterprise account in bug 1429335 resulted in: """ You have exceeded the limit of 100 members in your team mozillacorporation. To request an increase, please visit: https://www.heroku.com/contact?c=7013A000000mKrnQAE#sales """ Presumably we need to either: 1) Ask them to raise the limit 2) See if we can create multiple teams and link them together for billing purposes. (Like AWS or New Relic allows) 3) Delete inactive users from the team Chris, do you have any knowledge about #1/#2? If #2 were possible that might be a better long term solution, since it also resolves the current limitations with trying to restrict admin access to just those that need it (individual parts of the org could have their own sub-account etc).
Flags: needinfo?(chris.lonnen)
Reporter | ||
Comment 1•6 years ago
|
||
Hmm looks like the limit should be 500 not 100 for enterprise accounts: https://devcenter.heroku.com/articles/limits#membership-limits I'm guessing as part of giving us a higher limit in the past (before we switched to enterprise), they hardcoded a limit for us somewhere, that's now being used instead of 500. It seems like we should get them to double check (yet again) that all the necessary org->enterprise team changes were made (or customisations cleaned up).
Comment 2•6 years ago
|
||
filed: https://help.heroku.com/tickets/544374 will respond when I know. In the meanwhile I'm almost certain we have dead ldap accounts in the system for #3.
Flags: needinfo?(chris.lonnen)
Reporter | ||
Comment 3•6 years ago
|
||
Many thanks - could you email the "share" link for the ticket so I can view it? :-)
Comment 4•6 years ago
|
||
sent
Comment 5•6 years ago
|
||
ticket says they've bumped it to 500.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 6•6 years ago
|
||
I've also requested that they double check the other settings to ensure we don't have a third instance of this class of bug again. Also, before I open more tickets with Heroku asking about this, was there any mention of the below during the enterprise contract negotiation? (In reply to Ed Morley [:emorley] from comment #0) > 2) See if we can create multiple teams and link them together for billing > purposes. (Like AWS or New Relic allows)
Comment 7•6 years ago
|
||
Nothing beyond the existing features, no.
You need to log in
before you can comment on or make changes to this bug.
Description
•