Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider bypassing developer agreement check for langpacks upload #9459

Closed
diox opened this issue Feb 9, 2024 · 7 comments
Closed

Consider bypassing developer agreement check for langpacks upload #9459

diox opened this issue Feb 9, 2024 · 7 comments

Comments

@diox
Copy link
Member

diox commented Feb 9, 2024

https://bugzilla.mozilla.org/show_bug.cgi?id=1879549 happened because the developer agreement date changed on stage. Releng scripts that upload langpacks started to fail because their user had not accepted the agreement yet.

Their user is already part of a group giving them special rights. Should we have a special permission allowing them to bypass the developer agreement check entirely ?

┆Issue is synchronized with this Jira Task

@diox
Copy link
Member Author

diox commented Feb 9, 2024

@wagnerand
Copy link
Member

This sounds reasonable to me.

@diox
Copy link
Member Author

diox commented Feb 12, 2024

I think the simplest solution is to give set bypass_upload_restrictions=True on their user(s) on all envs. No additional code changes needed, this was intended to allow bypassing all restrictions, including developer agreement.

@wagnerand
Copy link
Member

I think the simplest solution is to give set bypass_upload_restrictions=True on their user(s) on all envs. No additional code changes needed, this was intended to allow bypassing all restrictions, including developer agreement.

I've done that now. One user had it already set, the other one didn't. I can't tell which one is the old user and which one is the new. Should we close this issue?

@diox
Copy link
Member Author

diox commented Feb 12, 2024

Did you do it on stage as well ? (I think the user is [email protected])

@wagnerand
Copy link
Member

Did you do it on stage as well ? (I think the user is [email protected])

I have now!

@diox diox closed this as completed Feb 12, 2024
@KevinMind
Copy link
Contributor

@KevinMind KevinMind transferred this issue from mozilla/addons-server May 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants