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

Expose max_allowed_packet to env vars. #1349

Merged
merged 7 commits into from Nov 26, 2019
Merged

Conversation

@steveworley
Copy link
Contributor

steveworley commented Oct 28, 2019

Allows max_allowed_packets to be overridden with an env var.

Checklist

Exposes an environment variable that can control the max_allowed_packet.

Changelog Entry

Improvement - Allow max_allowed_packet size to be controlled via env var.

Allows max_allowed_packets to be overridden with an env var.
@seanhamlin

This comment has been minimized.

Copy link
Contributor

seanhamlin commented Oct 28, 2019

Do we need docs on this? The docs could explain why this would be useful as well.

@Schnitzel

This comment has been minimized.

Copy link
Member

Schnitzel commented Nov 2, 2019

yes, the documentation PR has just been merged, so let's add that env variable to here: https://github.com/amazeeio/lagoon/blob/master/docs/using_lagoon/docker_images/mariadb.md

steveworley added 2 commits Nov 4, 2019
Add `MARIADB_MAX_ALLOWED_PACKET` to the list of environment variables.
@Schnitzel Schnitzel added this to the v1.2.0 milestone Nov 18, 2019
Schnitzel and others added 3 commits Nov 25, 2019
@Schnitzel Schnitzel merged commit 68fca5d into amazeeio:master Nov 26, 2019
1 check passed
1 check passed
continuous-integration/jenkins/pr-merge This commit looks good
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.