`pipe storage mount` incorrectly mounts storage when its name was specified with non-lower case
- Dominant language
- Java
- Stars
- 163
- Forks
- 65
- Avg merge
- 11h 46m
- Merged PRs (30d)
- 29
Description
**Describe the bug**
If the user tries to mount the storage via the `pipe` CLI using upper letters in its name (with `-b` option) no error appears, the command is being performed.
But then, if the user will try to access the storage via the mounted point - it will be unavailable.
It may confuse the user - e.g. in a case when the user just copied the storage name from the GUI where it was with different letter cases.
**To Reproduce**
Steps to reproduce the behavior:
1. Perform the command `pipe storage mount -b ` for an existing storage
2. See there are no errors
3. Perform the command `ls `
4. See the error `Invalid argument`
**Expected behavior**
The list of storage contents appears.
**Screenshots**
**Environment:**
- Cloud Provider: AWS
- Version 0.16.0.4573
- Browser: N/A
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.