Support for more adapters

[EldertGrootenboer]

Description

Currently only a very small set of adapters is supported, like FILE, FTP and HTTP.
However, for most of our clients we use the WCF based adapters.
Is there any way to work around this?

Environment and tool versions

• AIM Tool Version (aim --version):
• Windows Version (systeminfo):
• Shell: (PowerShell | Bash)
• Shell Version ($PSVersionTable | bash --version):

Repro steps

Use the tool with an MSI with WCF based adapters.

Expected result

Tool successfully processes the MSI with no errors.

Current result

The tool stops and outputs an error.

[probertdaniel]

Hi @EldertGrootenboer More Adapters are planned and some are on their way - we're already starting the planning work on how to implement WCF-BasicHttp and WCF-WebHttp.

What would be good to know is what basic features you'd like to see - because neither Logic Apps nor APIM implement a WCF stack, there's only a small amount that can be done without custom code e.g. can accept a SOAP request, unwrap it, work out SOAP Action and forward request.
But anything more complex (e.g. WS-* or cert based auth) will require more work.
There are two main options: 1) implement a subset of these adapters; 2) use an App Service to deploy the full WCF stack (using info from the BizTalk Bindings) and then have this forward requests to APIM/Logic Apps.
The second option above gives full support for WCF, but only for as long as App Services support .NET Framework.

What would be good to know is: what feature of the WCF-BasicHttp/WebHttp adapter are most important?