We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What would you like to be added: In order to make OSS API ready for production, we should add:
(P1) Docs
Features
Components
aliyun.oss
EcsRamRole
CI
.proto
chores
change the naming style from awsOSS to aws.s3
awsOSS
aws.s3
add comments for components/oss/oss.go Maybe one line comment which refers to some other doc is enough
components/oss/oss.go
These works can be done in some other PR instead of #556
Why is this needed: to make OSS API ready for production
The text was updated successfully, but these errors were encountered:
@wenxuwan We can continue with this issue
Sorry, something went wrong.
No branches or pull requests
What would you like to be added:
In order to make OSS API ready for production, we should add:
(P1) Docs
Features
Components
aliyun.oss
component supportEcsRamRole
; 让阿里云 OSS 组件不用配密钥 #748CI
.proto
files with specific protoc version. See feat: implement oss interface #556 (comment)chores
change the naming style from
awsOSS
toaws.s3
add comments for
components/oss/oss.go
Maybe one line comment which refers to some other doc is enough
These works can be done in some other PR instead of #556
Why is this needed:
to make OSS API ready for production
The text was updated successfully, but these errors were encountered: