-
Notifications
You must be signed in to change notification settings - Fork 45
pvsadm with a private cos endpoint #117
Copy link
Copy link
Open
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Metadata
Metadata
Assignees
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.Important over the long term, but may not be staffed and/or may need multiple releases to complete.
There is requirement of using the private cos endpoint instead for the secure private n/w use case, currently I see an option
--bucket-regionto supply the region, this option is used internally to build the cos URI, this task is to supply theprivate.prefix with this flag and make sure things are working fine(upload and import)e.g:
Public EP: s3.us-south.cloud-object-storage.appdomain.cloud
Private EP: s3.private.us-south.cloud-object-storage.appdomain.cloud
/cc @bpradipt
/assign @bkhadars