Bug #103742 Changing the default Sandbox directory doesn't work
Submitted: 19 May 2021 19:06 Modified: 20 May 2021 10:36
Reporter: Moorthy Vemparala Email Updates:
Status: Verified Impact on me:
None 
Category:Shell General / Core Client Severity:S3 (Non-critical)
Version:8.0.24, 8.0.25 OS:Windows (10)
Assigned to: CPU Architecture:x86 (64-bit Intel based )
Tags: instances, Sandbox directory

[19 May 2021 19:06] Moorthy Vemparala
Description:

Changing the default sandbox directory does not work. When creating the sandbox instances, it still shows/creates in the default directory. This happens when using the MySQL shell (Windows version) to create/deploy the sandbox instances.
Not sure if the same issue is there on the other platforms.

How to repeat:
 MySQL  JS > \c root@localhost:3306
Creating a session to 'root@localhost:3306'
Fetching schema names for autocompletion... Press ^C to stop.
Your MySQL connection id is 24
Server version: 8.0.24 MySQL Community Server - GPL
No default schema selected; type \use <schema> to set one.
 MySQL  localhost:3306 ssl  JS > \use sys
Default schema set to `sys`.

 MySQL  localhost:3306 ssl  sys  JS > \option sandboxDir
C:\Users\BVM\MySQL\mysql-sandboxes

 MySQL  localhost:3306 ssl  sys  JS > \option sandboxDir='C:\MySQL_Sandboxes'
 MySQL  localhost:3306 ssl  sys  JS > \option sandboxDir
'C:\MySQL_Sandboxes'

 MySQL  localhost:3306 ssl  sys  JS > dba.deploySandboxInstance(3307)
A new MySQL sandbox instance will be created on this host in
C:\Users\BVM\MySQL\mysql-sandboxes\3307

Warning: Sandbox instances are only suitable for deploying and
running on your local machine for testing purposes and are not
accessible from external networks.

Please enter a MySQL root password for the new instance:
 MySQL  localhost:3306 ssl  sys  JS >
[20 May 2021 10:36] MySQL Verification Team
Hello Moorthy,

Thank you for the report and feedback.

regards,
Umesh