mirror of
https://github.com/StackExchange/dnscontrol.git
synced 2025-12-27 02:58:46 +08:00
efe713cc0e
Either setting these new options OR using --notify on the commandline will send notification for any specific execution. Fixes #3906 In a second commit (feel free to remove) I added some logging to indicate that notifications were enabled or not (useful when testing each case). I've manually tested combinations of the various options, for both preview and push: * --notify set or unset on commandline * notify_on_* set to "true" or "ASDAS" or "false" or not mentioned All seem to provide the correct logging line - invalid boolean values are considered false (not an error). I've made an attempt at documentation of the options, not sure if you want it elsewhere as well. <!-- ## Before submiting a pull request Please make sure you've run the following commands from the root directory. bin/generate-all.sh (this runs commands like "go generate", fixes formatting, and so on) ## Release changelog section Help keep the release changelog clear by pre-naming the proper section in the GitHub pull request title. Some examples: * CICD: Add required GHA permissions for goreleaser * DOCS: Fixed providers with "contributor support" table * ROUTE53: Allow R53_ALIAS records to enable target health evaluation More examples/context can be found in the file .goreleaser.yml under the 'build' > 'changelog' key. !--> |
||
|---|---|---|
| .. | ||
| advanced-features | ||
| assets | ||
| commands | ||
| developer-info | ||
| getting-started | ||
| language-reference | ||
| markdown-examples | ||
| provider | ||
| release | ||
| .gitbook.yaml | ||
| index.md | ||
| SUMMARY.md | ||