Convert authorize variables to config system.

Variable references converted

+++ b/core/includes/authorize.incundefined
@@ -40,7 +40,7 @@ function authorize_filetransfer_form($form, &$form_state) {
-  elseif ($authorize_filetransfer_default = variable_get('authorize_filetransfer_default', NULL));

authorize_filetransfer_default isn't listed in the config file, is there a way to list it anyway, for discoveribility reasons.

+++ b/core/modules/system/config/system.authorize.ymlundefined
@@ -0,0 +1 @@
+allow_authorize_operations: TRUE

All config items are stored as strings. In most cases we choose '1' as true.

Yep we should list authorize_filetransfer_default in the yaml file if possible... and we can make the config names simple now they are in the system.authorise namespace.

• authorize_filetransfer_default can become filetransfer_default
• allow_authorize_operations can become allow_operations

Plus we need an update function to migrate the variables to config during a D7 to D8 upgrade see system_update_8009() as an example.

1. Added authorize_filetransfer_default to the config
2. Updated default of allow_authorize_operations to 1
3. Changed config names to filetransfer_default & allow_operations
4. Added a new update function system_update_9000 to migrate variables during a D8 upgrade

Hope the numbering is ok for the update hook, does this get reassigned before the final commit?

+++ b/core/modules/system/system.installundefined
@@ -2179,3 +2179,15 @@ function system_update_8029() {
+function system_update_9000() {

You're making a D7 to D8 upgrade function so the name of the upgrade function must be 8030 (if it isn't increased in the meantime)

Thanks aspilicious.

Updated system_update function to system_update_8030

fixed patch

Looks good to me. I hope I didn't missed something.

+++ b/core/includes/authorize.inc
--- /dev/null
+++ b/core/modules/system/config/system.authorize.yml

+++ b/core/modules/system/config/system.authorize.yml
@@ -0,0 +1,2 @@
+filetransfer_default:

Huh, interesting. Didn't know you could do that as an equivalent of NULL.

Committed and pushed to 8.x. Thanks! So great to see these conversion issues getting picked off, especially by new core contributors! :)