fix(serverless): set several environment variables in one rollout

[Ryank90]

Summary

• apps env set still sets one key with <key> --value or --value-file.
• Repeatable --env KEY=VALUE and --env-file read the current set, merge those keys, and write it in one request. Keys you do not mention stay. One rollout carries the whole change.
• A second apps env set while a rollout is already in progress still returns 409. That is the in-flight case, not two keys in one command.

Test plan

• runware serverless apps env set my-app --env FOO=bar --env BAZ=qux stores both, and a following apps env list still shows the keys that were already set
• apps env set my-app MY_KEY --value hello still sets one key
• Mixing <key> --value with --env is rejected

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. To trigger a review, include coderabbit-review in the PR description. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: da4e7718-8058-4fc9-89be-526441a558fc

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}