fix: keep Studio minimum instance at one - #949
Draft
evanlowe wants to merge 1 commit into
Draft
Conversation
evanlowe
force-pushed
the
fix/studio-min-instance-one
branch
from
August 20, 2026 10:50
b140688 to
9cecea5
Compare
evanlowe
force-pushed
the
fix/studio-min-instance-one
branch
from
August 20, 2026 10:54
9cecea5 to
5c6c8ac
Compare
yaozheng-fang
marked this pull request as draft
August 21, 2026 07:46
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
1 participant
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
MinInstanceto 1 after successful deploy and synchronous updatesMaxInstance,ReservedFrozenInstance, and all unrelated resource fieldsvefaas:UpdateFunctionResourceto Studio deploy precheck and runtime IAM policyvefaas:UpdateFunctionResource; other resource-update errors still stop the releaseLegacy deployment behavior
Existing Function roles cannot grant themselves new IAM permissions. For those deployments, an in-app update still publishes the new Revision but leaves
MinInstanceunchanged and records a warning. Runveadk studio updateonce, or grantvefaas:UpdateFunctionResourcemanually, to migrate the role and enforceMinInstance=1.Validation
pre-commit run --files ...MinInstance=1,MaxInstance=10MinInstance=1,MaxInstance=10MinInstance=1,MaxInstance=10