The pinpoint command supports reading a YAML configuration file that's referred to by the following means:
PINPOINT_USER_CONFIG environment variable.$XDG_CONFIG_HOME/pinpoint/config.yaml as the default location (this is platform dependent)NOTE: For up-to-date details, see the file config.go and in-source documentation.
The following YAML keys are supported:
| Key | Type | Description |
|---|---|---|
analyze_experiment | bool | Whether to perform statistical analysis on the differences between the base and experimental configurations. |
check_experiment | bool | Whether to return a non-zero command status if we can detect a statistically significant difference between the base and experimental configurations. |
download_artifacts | bool | Whether to download the artifacts of jobs when getting or starting them. |
download_results | bool | Whether to download the results of jobs when getting or starting them. |
endpoint | string | The fully qualified domain name of the gRPC service to connect to. |
open_results | bool | Whether to open the downloaded results with the default web browser. |
presets_file | string | The default file hosting presets. Learn more about presets at job-presets.md |
quiet | bool | Whether to suppress progress output. |
results_dir | string | The default directory where results should be downloaded (overrides the work_dir. |
select_artifacts | string | Which artifacts will be downloaded by default. |
wait | bool | Whether to always wait for scheduled or retrieved jobs to finish. |
work_dir | string | The default directory where files should be downloaded (overrides the default /tmp or equivalent directory in non-Unix platforms). |
These user configurations replace the defaults that would apply had the related flags been provided. To see what the current configuration options for a user are, you can invoke the config subcommand to see the flags that would have been default-applied when invoking subcommands.
$ pinpoint config