-
Notifications
You must be signed in to change notification settings - Fork 549
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs: add "Using Environment Variables". #2188
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding this @concretevitamin! It is very important to keep track of the environment variables we have.
Using in ``setup`` | ||
~~~~~~~~~~~~~~~~~~~~~~~~ | ||
|
||
All user-specified environment variables are exported to a task's ``setup`` commands. | ||
|
||
Using in ``run`` | ||
~~~~~~~~~~~~~~~~~~~~~~~~ | ||
|
||
All user-specified environment variables are exported to a task's execution (i.e., while its ``run`` commands are running). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we can combine the two sections into one to reduce the duplication.
Using in ``setup`` and ``run``
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call, done.
If a task is run as a :ref:`managed spot job <spot-jobs>`, then all | ||
recoveries of that job will have the same ID value. Read more :ref:`here <spot-jobs-end-to-end>`. | ||
- sky-2023-07-06-21-18-31-563597_myclus_id-1 | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are a bunch more env vars added by the #2106, but it should be fine to leave it out, as that feature is still experimental.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good.
Tested (run the relevant ones):
bash format.sh
pytest tests/test_smoke.py
pytest tests/test_smoke.py::test_fill_in_the_name
bash tests/backward_comaptibility_tests.sh