The --enabled-datastores and --disabled-datastores command parameters were recently added. They seem to work on Windows but perhaps not on Linux. Need to troubleshoot. Maybe the Linux tstool script is introducing a problem when it interprets the command line?
Also, for flexibility, may need to allow the order to be recognized. For example, to only enable one important datastore, would use --disabled-datastores=* and --enabled-datastores=somedatastore.
This was previously enhanced to allow multiple command line parameters to provide flexibility to enable and disable datastores with wildcards. Close this issue.
Subject of the issue
The
--enabled-datastores
and--disabled-datastores
command parameters were recently added. They seem to work on Windows but perhaps not on Linux. Need to troubleshoot. Maybe the Linuxtstool
script is introducing a problem when it interprets the command line?Also, for flexibility, may need to allow the order to be recognized. For example, to only enable one important datastore, would use
--disabled-datastores=*
and--enabled-datastores=somedatastore
.Environment