* System customization syncing for jobs run
* Constants moved
* Moving files
* Update src/lightning/app/runners/cloud.py
Co-authored-by: Adrian Wälchli <aedu.waelchli@gmail.com>
* Update test_cloud.py
* [pre-commit.ci] auto fixes from pre-commit.com hooks
for more information, see https://pre-commit.ci
* Update test_cloud.py
---------
Co-authored-by: Adrian Wälchli <aedu.waelchli@gmail.com>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
## What does this PR do?
Passes environment variables to the `CloudRuntime` when loading an app from a file. Allows apps / works / flows to be properly configured when passing variables at runtime.
### Limitations
- Only implemented for the `CloudRuntime`
<details>
<summary><b>Before submitting</b></summary>
- Was this **discussed/agreed** via a GitHub issue? (not for typos and docs)
- [ ] Did you read the [contributor guideline](https://github.com/Lightning-AI/lightning/blob/master/.github/CONTRIBUTING.md), **Pull Request** section?
- [ ] Did you make sure your **PR does only one thing**, instead of bundling different changes together?
- Did you make sure to **update the documentation** with your changes? (if necessary)
- Did you write any **new necessary tests**? (not for typos and docs)
- [ ] Did you verify new and **existing tests pass** locally with your changes?
- Did you list all the **breaking changes** introduced by this pull request?
- Did you **update the CHANGELOG**? (not for typos, docs, test updates, or minor internal changes/refactors)
<!-- In the CHANGELOG, separate each item in the unreleased section by a blank line to reduce collisions -->
</details>
## PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the [review guidelines](https://github.com/Lightning-AI/lightning/wiki/Review-guidelines). In short, see the following bullet-list:
<details>
<summary>Reviewer checklist</summary>
- [ ] Is this pull request ready for review? (if not, please submit in draft mode)
- [ ] Check that all items from **Before submitting** are resolved
- [ ] Make sure the title is self-explanatory and the description concisely explains the PR
- [ ] Add labels and milestones (and optionally projects) to the PR so it can be classified
</details>
<!--
Did you have fun?
Make sure you had fun coding 🙃
-->
cc @borda
dependabot[bot]