Custom APIM for commercetools config about commercetools-dotnet-core-sdk-v2 HOT 6 CLOSED

Hi @MicheleRezk
many thanks for your effort in confirming that, for some reasons, we have decided not to use custom api-gateway, but to call commercetools directly.

So this is no longer an issue, nevertheless like you have mentioned there shouldn't be a problem as the URL's are not written.

from commercetools-dotnet-core-sdk-v2.

Hello @theburhan,As per documentation, you would select Api Url based on the host Region, so I'm just wondering why would you do a custom API gateway like your example?

from commercetools-dotnet-core-sdk-v2.

Hi @MicheleRezk, I actually want to decouple dotnet service from CT via custom API gateway for two reasons, first, so that in future if for any reason I want to decommission some services from CT in favour of another external system, then dotnet service won't be affected, I will only have to update the APIM with a different target URL, so APIM here is only treated as proxy call.

Also, I will be using mock server for e2e integration tests, where I want to avoid making calls to CT. So, in the config on our test env, APIM will be making proxy calls to stubs.

I already tested that flow with SDK1, where it was working fine. Is that really a defect in SDK2 that overwrites the ApiBaseUrl or do you think it is done on purpose because having a custom APIM in this use-case is not a good practice?

from commercetools-dotnet-core-sdk-v2.

and the second case is, my service will be deployed in VNET which has no access to the internet. So, I want to make proxy call.

from commercetools-dotnet-core-sdk-v2.

Hi @theburhan,
I already checked the issue and found that we're not replacing the BaseAddress in the client, it will be same as configured in the appsettings.json, please check attached screenshot while debugging it.

from commercetools-dotnet-core-sdk-v2.

Hi @theburhan ,

Do you still having an issue or should I close it?

from commercetools-dotnet-core-sdk-v2.