JinyuChen97 commented on code in PR #8500:
URL: https://github.com/apache/camel-quarkus/pull/8500#discussion_r3032376212


##########
integration-tests/ibm-cos/src/main/java/org/apache/camel/quarkus/component/ibm/cos/it/IBMCloudObjectStorageRoutes.java:
##########
@@ -69,9 +74,37 @@ public void configure() throws Exception {
         from("direct:list")
                 .to(componentUri(IBMCOSOperations.listObjects));
 
+        from("direct:delete-objects")
+                .to(componentUri(IBMCOSOperations.deleteObjects));
+
+        from("direct:copy-object")
+                .to(componentUri(IBMCOSOperations.copyObject));
+
+        from("direct:get-object-range")
+                .to(componentUri(IBMCOSOperations.getObjectRange));
+
+        from("direct:list-buckets")
+                .to(componentUri(IBMCOSOperations.listBuckets));
+
+        from("direct:put-object-autocreate")
+                
.to(componentUriWithAutoCreate(IBMCOSOperations.putObject).keyName(KEY_FOR_AUTOCREATE));
+
+        from("direct:read-autocreate")
+                
.to(componentUriWithAutoCreate(IBMCOSOperations.getObject).keyName(KEY_FOR_AUTOCREATE));
+
+        from("direct:delete-object-autocreate")
+                
.to(componentUriWithAutoCreate(IBMCOSOperations.deleteObject).keyName(KEY_FOR_AUTOCREATE));
+
+        from("direct:delete-bucket-autocreate")
+                .to(componentUriWithAutoCreate(IBMCOSOperations.deleteBucket));

Review Comment:
   sorry, I missed the 'object' in direct-read-autocreate route, it's actually 
for get objects. All object operations routes will need to have keyname of 
which object is processed, it's the key of object. Bucket operation doesn't 
need the key of object. I will improve the name "direct:read-autocreate" to 
"direct:read-object-autocreate" to make it more clear and consistent with other 
object operation routes.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to