fix(databases): clarify autoscaling max is an absolute cap (DAT-1770)#3124
Closed
abnegate wants to merge 1 commit into
Closed
fix(databases): clarify autoscaling max is an absolute cap (DAT-1770)#3124abnegate wants to merge 1 commit into
abnegate wants to merge 1 commit into
Conversation
The maximum storage input read as headroom above current storage; add helper text stating it is the absolute total size the volume may grow to, at which autoscaling stops. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
Greptile SummaryThis PR clarifies the dedicated database autoscaling storage cap. The main changes are:
Confidence Score: 5/5This looks safe to merge.
Important Files Changed
Reviews (1): Last reviewed commit: "fix(databases): clarify autoscaling max ..." | Re-trigger Greptile |
Member
Author
|
CI note: the three failing checks (build, e2e, console-stage) are the base branch's baseline — |
Member
Author
|
Closing per maintainer decision — the base branch (feat-dedicated-db) is baseline-red and this is a 1-line copy tweak; will be folded into the feature branch's own polish instead of carried as a standalone PR. |
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.
What
Adds helper text to the "Maximum storage (GB)" input in the dedicated database storage autoscaling settings, clarifying that the value is the absolute total size the volume may grow to — not headroom above current storage.
Before: label "Maximum storage (GB)" with no helper text.
After: same label, with helper: "The maximum total size this database's storage can grow to. Autoscaling stops at this limit."
Why
Fixes DAT-1770 — the input read as an amount of headroom to add above current storage, when it is actually the absolute cap at which autoscaling stops.
Copy-only change, no behavior.
🤖 Generated with Claude Code