Bug #114685 Let InnoDB Cluster configure GIPK=ON and disabled_storage_engines='MyISAM'
Submitted: 18 Apr 2024 15:20 Modified: 19 Apr 2024 14:10
Reporter: Keith Hollman Email Updates:
Status: Verified Impact on me:
None 
Category:Shell AdminAPI InnoDB Cluster / ReplicaSet Severity:S4 (Feature request)
Version:8.0.36 OS:Any
Assigned to: CPU Architecture:Any

[18 Apr 2024 15:20] Keith Hollman
Description:
When running the "dba check-instance-configuration" and "dba configure-local-instance" it would be nice to receive the option to enforce InnoDB Cluster protection against 'breakable' options that can take nodes out, such as creating MyISAM tables and then inserting rows or allowing GIPK's to be ON but have show_gipk_in_create_table_and_information_schema = OFF.

How to repeat:
I'm migrating Drupal environments into an InnoDB Cluster from MariaDB and I want to avoid any risk of MyISAM table creation and also I want to enforce PK usage via sql_generate_invisible_primary_key=ON but I have to do this after running the checkInstanceConfiguration and ConfigureLocalInstance. 

Suggested fix:
Seeing as ConfigureLocalInstance configures and restarts the instance, surely this could be asked or included as a possible option when executing the command? Eg.
mysqlsh icadmin@localhost:3306 -- dba configure-local-instance --restart=true --interactive=FALSE --Enforce=DisableMyISAM,GIPK_On
[19 Apr 2024 14:11] MySQL Verification Team
Thanks.