Fill gaps from assistant conversations: scaler value and Pod min fields - #835
Open
mintlify[bot] wants to merge 2 commits into
Open
Fill gaps from assistant conversations: scaler value and Pod min fields#835mintlify[bot] wants to merge 2 commits into
mintlify[bot] wants to merge 2 commits into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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.
Summary
Closes two recurring documentation gaps surfaced by assistant conversations: valid scaler value range for Serverless auto-scaling, and the semantics of
min*inputs in the GraphQL Pod deploy mutation.Changes
serverless/endpoints/endpoint-configurations.mdx: state that the scaler value must be a whole number ≥ 1 (default 4), matching the OpenAPI spec (scalerValue: integer, minimum 1).sdks/graphql/manage-pods.mdx: explain thatminVcpuCount/minMemoryInGbare minimum machine-matching requirements, not fixed allocations.Context
Other themes reviewed (Terraform, Kubernetes, BAA/HIPAA, storage throughput numbers) had no verifiable facts in the repo, so no changes were made for them.