Add dask config set

[milesgranger]

• Closes CLI to get/set dask config values #9746
• Tests added / passed
• Passes pre-commit run --all-files

---

• CLI to set config values. ie. dask config set dataframe.query-planning-warning False.

[github-actions]

Unit Test Results

See test report for an extended history of previous test failures. This is useful for diagnosing flaky tests.

     15 files  ±  0       15 suites  ±0   3h 24m 46s ⏱️ + 5m 59s
 13 040 tests +  8   12 109 ✅ +  8     931 💤 ±0  0 ❌ ±0 
161 287 runs  +120  144 752 ✅ +119  16 535 💤 +1  0 ❌ ±0 

Results for commit 2804fab. ± Comparison against base commit 76b255e.

♻️ This comment has been updated with latest results.

[crusaderky]

The new command dumps out your whole dask config to ~/.config/dask/dask.yaml.

I would like to treat this as an antipattern, as it will cause many problems down the line when some developer changes a default of some obscure setting but the users don't pick up the change. What's worse, wiping and rebuilding the conda environment won't reflect the change. Also, the user will have no indication, when they do open that config file, about which settings were their own intentional changes from a month before and which were just copy-pasted defaults.

Could you change the code to add the new explicit config override to whatever was already there in ~/.config/dask/dask.yaml, but nothing in addition to that?

Finally, could you document the new command in docs/source/configuration.rst?

[milesgranger]

Thanks for the review @crusaderky, clearly the CLI will take a bit more work, so I've moved the config option over to #10925.

The new command dumps out your whole dask config to ~/.config/dask/dask.yaml.

Indeed, I wasn't sure if this was correct either but saw this is the same flow being done with coiled config set and thus followed suit. And will anyway address this and the remainder later today.

[crusaderky]

Could you document the new command in docs/source/configuration.rst?
Everything else LGTM

[milesgranger]

Could you document the new command in docs/source/configuration.rst?

Ah nuts, sorry I'd forgotten that, done now.

[mrocklin]

cc @jacobtomlinson @ntabris

[ntabris]

this should link to #9746 rather than #10917, right?

[ntabris]

The new command dumps out your whole dask config to ~/.config/dask/dask.yaml.

Indeed, I wasn't sure if this was correct either but saw this is the same flow being done with coiled config set

FYI that's not what coiled config set does: