fix(serverless): describe apps scale as a version and a rollout - #128
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 |
65e7b3d to
55e2418
Compare
504905c to
cd80f61
Compare
55e2418 to
6ed36ac
Compare
cd80f61 to
d50116a
Compare
b73fdcd to
9994eb7
Compare
Help said a configuration change waited for the next scaler cycle. The API records a new version with the same image and rolls the workload.
Co-authored-by: Wilson Silva <wilson.dsigns@gmail.com>
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.
…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.
9994eb7 to
c51c0c3
Compare
Summary
apps scalehelp now says a configuration change records a new version with the same image and rolls the workload, instead of waiting for the next scaler cycle.Test plan
runware serverless apps scale --helpdescribes a version and a rollout, and says the command does not wait for it