You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.
It should be pointed out that the COS_ENDPOINT meant here is obtained by going to the COS / Endpoint menu item in the UI...
not the Endpoints in credentials
Actually it's even more confusing, cause I think this is the correct location, on the config page of the bucket itself, and there's a choice between public, private, direct???
It's also here I think that the IAM_ROLE_CRN is taken from???? instead as the one from the credentials file?
and a 3rd point of confusion is that the COS instance has an api key for the whole instance AND just one for the Bucket... it should be pointed out which API KEY should be used here!!!
The text was updated successfully, but these errors were encountered:
remkohdev
changed the title
COS_ENDPOINT format example should be similar to COS Credentials
COS_ENDPOINT is NOT the COS_ENDPOINT in COS Credentials but the endpoint in UI/COS/Endpoint
Apr 12, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
E.g. the .env config for COS_ENDPOINT suggest an example
but the COS credentials lists the following endpoint
It should be pointed out that the COS_ENDPOINT meant here is obtained by going to the COS / Endpoint menu item in the UI...
not the Endpoints in credentials
Actually it's even more confusing, cause I think this is the correct location, on the config page of the bucket itself, and there's a choice between public, private, direct???
It's also here I think that the IAM_ROLE_CRN is taken from???? instead as the one from the credentials file?
and a 3rd point of confusion is that the COS instance has an api key for the whole instance AND just one for the Bucket... it should be pointed out which API KEY should be used here!!!
The text was updated successfully, but these errors were encountered: