[1:21 PM] Harris, Nathan (TR Tech, Content & Ops)
    Sorry I was stuck in a debate
​[1:22 PM] Harris, Nathan (TR Tech, Content & Ops)
    what's up ?
​[1:25 PM] Nikolaev, Viktor
    We wanted to integrate our new cool httpClient with proxy to automations.
	As I can see, we only need to change engines themselves - I see there are methods like CreateHttpClient

​[1:26 PM] Harris, Nathan (TR Tech, Content & Ops)
    Yeah there should be central code in each WFE that we need to configure
​[1:26 PM] Harris, Nathan (TR Tech, Content & Ops)
    The automations themselves only access web via WFEs
​[1:29 PM] Nikolaev, Viktor


Ok, cool.
Also what should we do if proxy settings in Elastic get updated?

Ie we have to subscribe for changes and update HttpClientHandler on a running automations? Or we can just restart running automation so it will pick-up new settings?

Edited​[1:38 PM] Harris, Nathan (TR Tech, Content & Ops)
    It doesnt have to be dynamic
​[1:39 PM] Harris, Nathan (TR Tech, Content & Ops)
    new config can be picked up on next run
​[1:39 PM] Harris, Nathan (TR Tech, Content & Ops)
    I believe all day schedules will get bounced if the schedule is changed
​[1:39 PM] Harris, Nathan (TR Tech, Content & Ops)
    check with Viktor
[1:39 PM] Harris, Nathan (TR Tech, Content & Ops)
    *Vladimir
​[1:39 PM] Harris, Nathan (TR Tech, Content & Ops)
    (smile)

​[1:39 PM] Harris, Nathan (TR Tech, Content & Ops)
    checking with yourself might not be very productive!
​[1:41 PM] Nikolaev, Viktor
    Currently in a Schedule we have ProxyId, so if we change something in the Proxy index, it would not update the Schedule. Do we need to bounce the Schedule manually in Scheduler?
​[1:47 PM] Harris, Nathan (TR Tech, Content & Ops)
    If it's by ID then I assume the automation when it starts will pull the latest proxy information on startup from the config
​[1:47 PM] Harris, Nathan (TR Tech, Content & Ops)
    However change to proxy for all day schedules wouldn't restart them
​[1:48 PM] Harris, Nathan (TR Tech, Content & Ops)
    so maybe scheduler should get notifcation of change and take action
​[1:48 PM] Harris, Nathan (TR Tech, Content & Ops)
    I think it's only the all day ones where we need to capture this
​[1:49 PM] Nikolaev, Viktor
    Yeap, so the question is - should we just restart automation (easy way), or we need to subscribe for changes in automation itself?
​[1:49 PM] Harris, Nathan (TR Tech, Content & Ops)
    I think we get scheduler to subscribe and do the restart of all days
[1:49 PM] Harris, Nathan (TR Tech, Content & Ops)
    If we subscribe in automation then we may disrupt current running
​[1:50 PM] Harris, Nathan (TR Tech, Content & Ops)
    which probably isnt desirable
​[1:50 PM] Harris, Nathan (TR Tech, Content & Ops)
    although it would be cool
​[1:51 PM] Nikolaev, Viktor
    We won't disrupt current running as new proxy settings will be used on next http call
​[1:53 PM] Harris, Nathan (TR Tech, Content & Ops)
    ic OK - maybe this a better option
​[1:53 PM] Harris, Nathan (TR Tech, Content & Ops)
    only concern is someone changes proxy and breaks all running automatiosn
​[1:53 PM] Harris, Nathan (TR Tech, Content & Ops)
    I suppose risk is the same if change is made on next run
​[1:54 PM] Harris, Nathan (TR Tech, Content & Ops)
    I assume if the notification is delete then we ignore in automation ?
​[1:54 PM] Harris, Nathan (TR Tech, Content & Ops)
    or we switch to no proxy mode ?
​[1:55 PM] Nikolaev, Viktor
    Not sure what is better. Let's switch to no proxy.