-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(iot-service): Add proxy support for registry manager #768
Conversation
/azp run |
Azure Pipelines successfully started running 4 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
@@ -41,6 +44,10 @@ | |||
private ExecutorService executor; | |||
private IotHubConnectionString iotHubConnectionString; | |||
|
|||
@Setter |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a standard order in which to list these? I'd have assumed get would be first, if there was.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There isn't a standard that I know of, unlike in C#. I can switch them if it's bugging you though
/azp run |
Azure Pipelines successfully started running 4 pipeline(s). |
Not for service client, just for registry manager
see #766