All the api to api calls are now using TLS + SAT. We do this by initializing an overall apiclient with the symphony api address set in the pod env parameter.
We keep the http + user creds for child and parent communications since TLS + SAT by default doesn't work. The reason why we don't use an overall apiclient for parent calls is that parent urls may change. (Thought it doesn't work like this now) That's why we think singleton doesn't apply to parent-children apiclient.
Definitely some corresponding tests changes. I manually tested the multisite scenario.
All the api to api calls are now using TLS + SAT. We do this by initializing an overall apiclient with the symphony api address set in the pod env parameter.
We keep the http + user creds for child and parent communications since TLS + SAT by default doesn't work. The reason why we don't use an overall apiclient for parent calls is that parent urls may change. (Thought it doesn't work like this now) That's why we think singleton doesn't apply to parent-children apiclient.
Definitely some corresponding tests changes. I manually tested the multisite scenario.