ank19 commented on PR #9541:
URL: https://github.com/apache/camel/pull/9541#issuecomment-1471497702

   @oscerd - Sure, I also stumbled across the validateConfiguration method. 
Even if it's embarrassing, but I have to confess that on the fly I just derived 
a class from the configuration
   ```
   @ConfigurationProperties(prefix="camel.component.azure-storage-datalake")
   @Profile("!test")
   public class Azure extends DataLakeConfiguration ...
   ``` 
   and then I registered the component manually:
   ```
   final var sharedKeyCredential = new 
StorageSharedKeyCredential(getAccountName(), getAccountKey());
   final var builder = new DataLakeServiceClientBuilder();
   builder.credential(sharedKeyCredential);
   builder.endpoint("https://"; + getAccountName() + ".dfs.core.windows.net");
   final var dataLake = new DataLakeComponent(context);
   setServiceClient(builder.buildClient());
   dataLake.setConfiguration(this);
   context.addComponent("datalake", dataLake);
   ```
   Would it be possible to change that validate method so that setting the 
accountKey passes the validation and to create a StorageSharedKeyCredential 
from that then?


-- 
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: commits-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to