-
Couldn't load subscription status.
- Fork 737
Update maximum galaxy artifact size #3099
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
Conversation
|
That's correct, we defined that size based on observation of maximum of existing collections. |
|
@rochacbruno Thanks for confirming. |
Backport to stable-2.17: 💚 backport PR created✅ Backport PR branch: Backported as #3176 🤖 @patchback |
(cherry picked from commit 3603994)
Backport to stable-2.19: 💚 backport PR created✅ Backport PR branch: Backported as #3177 🤖 @patchback |
(cherry picked from commit 3603994)
Backport to stable-2.20: 💚 backport PR created✅ Backport PR branch: Backported as #3178 🤖 @patchback |
(cherry picked from commit 3603994)
(cherry picked from commit 3603994) Co-authored-by: Sloane Hertel <[email protected]>
(cherry picked from commit 3603994) Co-authored-by: Sloane Hertel <[email protected]>
(cherry picked from commit 3603994) Co-authored-by: Sloane Hertel <[email protected]>
Backport to stable-2.18: 💚 backport PR created✅ Backport PR branch: Backported as #3179 🤖 @patchback |
(cherry picked from commit 3603994)
I'm not sure if this is correct for community Galaxy (200 MB is documented for Hub ansible/aap-docs#4558), so someone with access to wherever the max size is now defined should confirm this change. 2 MB has been out of date since ansible/galaxy@6ca6b97.
CC @rochacbruno