fix(serverless): set secrets and scale knobs on deploy create - #132
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. To trigger a review, include ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
225f0f4 to
cfec75b
Compare
A first deploy could not attach an organisation secret or set the worker buffer, concurrency, or fallback GPU, and the help did not say that volumes stay fixed after create.
cfec75b to
d309973
Compare
55e2418 to
6ed36ac
Compare
…orker percent An httptest now decodes the create body for secrets and minAvailableWorkers. --available-workers-pct is checked locally so a value outside 0-100 fails before the archive upload.
Summary
deploycan attach organisation secrets at create with--secret NAMEor--secret NAME=ENV_VAR, so the first rollout carries them.apps scalealready has:--concurrency,--fallback-gpu-type,--min-available-workers, and--available-workers-pct. Passing any of them on an update is rejected.Test plan
--secret ORG_TOKENand--min-available-workers 1sends those fieldssecrets attachorapps scale--volumeon an update says volumes are immutable after create