fix: fixes an issue where 'ls' may return "string index out of range"
Type of change
-
Bug Fix -
Feature -
Pipeline -
Test
Does this introduce a change in the core logic?
-
No -
Yes
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
Does this follow conventional commits spec?
- [X ] No
-
Yes
Have you set the target Milestone?
-
No -
Yes
Have you set the no-detached-pipeline label?
-
No -
Yes
Updates description?
- Make utility/ls case strictly sensitive across the board including dataset, path, tenant, subproject.
- Return empty result when current case-sensitive path doesn't exist.
- Make Azure result same behavior as GCP side