Repository navigation
feat(api7ee): add server.max_request_body_size to dashboard and developer portal config - #431
Draft
jarvis9443 wants to merge 1 commit into
Draft
jarvis9443 wants to merge 1 commit into
jarvis9443 wants to merge 1 commit into
Conversation
…oper portal config Mirrors api7/api7ee-3-control-plane#3163, which lists the key in the upstream helm/values.yaml.
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Syncs the new control-plane config key
server.max_request_body_sizeintocharts/api7/values.yaml, under bothdashboard_configuration.serveranddeveloper_portal_configuration.server, right after thepprofblock. The text matches the CP's upstreamhelm/values.yamlexactly, default33554432bytes (32 MiB); a request body larger than that gets a 413.The default equals the CP's built-in default, so a default render doesn't change behaviour. It only makes the limit visible and settable. The chart README is regenerated with helm-docs. The chart version isn't bumped here: this PR is held and gets folded into the 3.10 release PR, which does the bump.
Hold-for-release: api7/api7ee-3-control-plane#3163