[Meta] - 8.0 Upgrade Assistant

[kobelb]

THIS ISSUE HAS BEEN ABANDONED see #67915 (comment)

Hey everyone! I'd like to use this issue to track everything that we need to make sure is taken into consideration when performing the 8.0 upgrade, particularly breaking changes. I've seeded the list with what I've found so far, please add comments with new items you'd like added.

Kibana Security

• Remove kibana_user role (replaced with kibana_admin role).
• Remove kibana user (replaced with kibana_system user)
• Remove "Dashboard only mode" (and associated kibana_dashboard_only_user role), in favor of "Feature Controls", which we introduced in 7.2
• Remove support for deprecated xpack.security.authc.providers array-based configuration, in favor of the more verbose configuration introduced in Implement Kibana Login Selector #53010

Operations

• Settings use snake_case Settings should use snake_case #7444
• Move keystore to config directory Move kibana.keystore to the configuration directory #25746

Platform

• A couple of fields in the Saved Objects import/export API will be changed to snake case. This API is marked as "experimental" but we would still prefer to do this as a breaking change in 8.x.
  Use snake case for saved objects import/export API #54123
• Remove an older Kibana "dashboard import/export API"
  Remove Dashboard Import/Export API #41439
• The instructions for doing a Kibana version rollback will change. In 7.x it was possible to do a rollback after a failed upgrade without using snapshots, in 8.x users will have to restore a snapshot in order to do a rollback.
  RFC: Improve saved object migrations #66056
• Refactor Kibana's config "namespaces" [New Platform] 8.0 Refactor kibana.yml #46705
• plugin id format has been changed from snake_case to camelCase. Users might have to update their config plugin_name.enabled ==> pluginName.enabled.
• formalize error response format Formalize HTTP error response format #57296

[kobelb]

/cc @legrego @joshdover @tylersmalley @mikecote @joelgriffith @TinaHeiligers @ryankeairns

[legrego]

I think we should also track #54702, since we need a way to surface these deprecations in the UA

[mshustov]

• plugin id format has been changed from snake_case to camelCase. Users might have to update their config plugin_name.enabled ==> pluginName.enabled.
• formalize error response format Formalize HTTP error response format #57296

[rayafratkina]

Should Timelion deprecation and the need for a warning during upgrade be tracked here?

[kobelb]

After discussing further with @cjcenizal, we've decided to collect these requirements using separate GitHub issues for each deprecation. There's now an 8.0 Breaking change issue template that should be used to create these issues.

I went ahead and converted a few of the Kibana Security issues to the new format to refine the aforementioned template. I've converted the list of deprecations in the primary issue description to a check-list, and checked off the issues which have been converted. If you all wouldn't mind doing the same with your respective issues, I'd greatly appreciate it.

[cjcenizal]

Seems like this is obsolete now? @kobelb Please feel free to reopen if this issue is still in active use.