Matthew Jacobson 5a80962de9 Alerting: Add clean_upgrade config and deprecate force_migration (#78324) ... * Alerting: Add clean_upgrade config and deprecate force_migration Upgrading to UA and rolling back will no longer delete any data by default. Instead, each set of tables will remain unchanged when switching between legacy and UA. As such, the force_migration config has been deprecated and no extra configuration is required to roll back to legacy anymore. If clean_upgrade is set to true when upgrading from legacy alerting to Unified Alerting, grafana will first delete all existing Unified Alerting resources, thus re-upgrading all organizations from scratch. If false or unset, organizations that have previously upgraded will not lose their existing Unified Alerting data when switching between legacy and Unified Alerting. Similar to force_migration, it should be kept false when not needed as it may cause unintended data-loss if left enabled. --------- Co-authored-by: Christopher Moyer <35463610+chri2547@users.noreply.github.com>		2023-11-30 11:01:11 -05:00
..
configure-custom-branding	Docs: copy edit (#76652)	2023-10-26 10:50:31 -05:00
configure-tracing	Explicitly set all front matter labels in the source files (#71548)	2023-07-18 09:10:12 +01:00
enterprise-configuration	Doc: Add docs for direct mapping of None role for SAML (#76551)	2023-10-13 16:01:55 +01:00
feature-toggles	Alerting: Remove old contact points view (#78704)	2023-11-30 13:37:14 +01:00
proxy	Explicitly set all front matter labels in the source files (#71548)	2023-07-18 09:10:12 +01:00
settings-updates-at-runtime	Explicitly set all front matter labels in the source files (#71548)	2023-07-18 09:10:12 +01:00
_index.md	Alerting: Add clean_upgrade config and deprecate force_migration (#78324)	2023-11-30 11:01:11 -05:00