[ 
https://issues.apache.org/jira/browse/CAMEL-14912?focusedWorklogId=424052&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-424052
 ]

ASF GitHub Bot logged work on CAMEL-14912:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 17/Apr/20 09:08
            Start Date: 17/Apr/20 09:08
    Worklog Time Spent: 10m 
      Work Description: jamesnetherton commented on pull request #3757: 
CAMEL-14912: Allow custom service URIs to be used with Azure clients
URL: https://github.com/apache/camel/pull/3757
 
 
   https://issues.apache.org/jira/browse/CAMEL-14912
 
----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

            Worklog Id:     (was: 424052)
    Remaining Estimate: 0h
            Time Spent: 10m

> Azure components should allow custom service URIs
> -------------------------------------------------
>
>                 Key: CAMEL-14912
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14912
>             Project: Camel
>          Issue Type: Improvement
>            Reporter: James Netherton
>            Assignee: James Netherton
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> If you provide custom blob or queue clients to the Azure components, it seems 
> you're forced to configure a service URI for either {{blob.core.windows.net}} 
> or {{queue.core.windows.net}} This is validated in 
> {{QueueServiceUtil.prepareStorageQueueUri}} & 
> {{BlobServiceUtil.prepareStorageBlobUri}}.
> This prohibits testing with the Azure storage emulator where you'd configure 
> a custom client with a URI that likely points at localhost. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to