You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to capture some suggestions on how to improve the config file system to better work in large repos and organizations
Instead of the system only being configured in the file located at SKYPILOT_CONFIG, first look for a .skypilot.yaml dotfile in the pwd. The CLI should also accept a --config FILENAME option. They should be parsed and merged in the order of priority (flag, dotfile, user dir file).
All settings in the global config should be overridable in a task.yml
sky check should only look at clouds configured in the global config
Users should be able to specify the cloud target metadata in each task.yml. For example, a user should be able to set GCP project ID per task, instead of having to use the GOOGLE_PROJECT_ID env var
The text was updated successfully, but these errors were encountered:
Trying to capture some suggestions on how to improve the config file system to better work in large repos and organizations
SKYPILOT_CONFIG
, first look for a.skypilot.yaml
dotfile in the pwd. The CLI should also accept a --config FILENAME option. They should be parsed and merged in the order of priority (flag, dotfile, user dir file).sky check
should only look at clouds configured in the global configThe text was updated successfully, but these errors were encountered: