Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

关于alias别名的独立挂载开放写入权限的建议 #7574

Open
4 tasks done
basic011 opened this issue Nov 28, 2024 · 0 comments
Open
4 tasks done

关于alias别名的独立挂载开放写入权限的建议 #7574

basic011 opened this issue Nov 28, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@basic011
Copy link

basic011 commented Nov 28, 2024

Please make sure of the following things

  • I have read the documentation.
  • I'm sure there are no duplicate issues or discussions.
  • I'm sure this feature is not implemented.
  • I'm sure it's a reasonable and popular requirement.

Description of the feature / 需求描述

alias别名如果每个别名只挂载了一个存储空间,应该可以写入
我天翼云盘用本地代理模式挂载到/ecloud/兼容通道,用302模式挂载到/ecloud/高速通道。目前通过以下写法方式挂载:
/alias/xxx用户组/高速通道:/ecloud/高速通道/xxx用户组专用
/alias/xxx用户组/兼容通道:/ecloud/兼容通道/xxx用户组专用
发现只可读,不可写。逻辑上来讲,如果一个别名只聚合了一个目录,是可以写入的。
在这种模式下发现一个BUG:兼容通道并没有按照期望走到本机代理模式下,而是走在302模式下。

Suggested solution / 实现思路

1.写入问题,建议在创建alias存储那里添加一个可写入选项,在勾选此选项后,限制每个别名只能挂载一个目录。
2.BUG问题,猜测目前逻辑是一个alias存储扫描,如果有302就优先302.按照文档的描述,实际逻辑应该每一个alias别名分别判断,比如一个alias存储下我声明了两个不同的聚合目录,应该每个目录单独判断,而不是整个alias存储判断优先方式。

Additional context / 附件

No response

@basic011 basic011 added the enhancement New feature or request label Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant