Repository navigation
Match planned Cloud CPU and memory to public pricing - #369
Merged
Merged
Conversation
rmcdaniel
marked this pull request as ready for review
October 23, 2026 08:22
|
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.
The documentation still gives Standard and Multi-Region half the CPU and memory shown on public Cloud pricing. Update those two capacity cells to 2 vCPU and 4 GB RAM in all eight languages.
All storage, price, qualification and planned-availability fields are preserved, along with Cloud Dev and both Business rows. This changes documentation only; it does not change commercial terms or provisioning. The public pricing response was checked directly on October 23, and reviewed source hashes and executable examples pass locally.
Refs #345. Exact-head documentation qualification 39924468998 passes the all-eight-locale build and strict links; all other checks pass, including Sonar with zero new issues/hotspots. The comparison verifies that only the sixteen CPU/memory cells and their source hashes change. Live localized-table verification follows deployment.