Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Use an Airflow config to manage provider configuration (#41)
Before this change, the provider used standard operating system environment variables to receive user configuration. This PR changes these to Airflow config, which already gracefully handles booleans and supports setting the configuration via environment variables and via `airflow.cfg`. This PR introduces these changes: * Replace `ANYSCALE__AIRFLOW_TELEMETRY_ENABLED` by `AIRFLOW__ANYSCALE__CLI_TOKEN` (or equivalent `airflow.cfg`) * Support `AIRFLOW__ANYSCALE__CLI_TOKEN` (or equivalent `airflow.cfg`) as an alternative to `ANYSCALE_CLI_TOKEN` Note: the following is discussed in a separate PR (#42), so I removed changing the default value for telemetry from the current PR. ~~The current documentation needs to provide more information about the telemetry and data collection, which is a crucial aspect that needs to be addressed.~~ ~~Until the following questions are addressed, I believe it should be disabled by default:~~ ~~* How does enabling telemetry help users?~~ ~~* Where is the data being sent?~~ ~~* What data is being collected?~~ ~~* How is the data being used?~~
- Loading branch information