Azure-cli: Add trusted origin to direct line channel without using Azure portal

[ericchansen]

Is your feature request related to a problem? Please describe.

I need to be able to stand up a bot and the associated web page from an Azure DevOps pipeline. The Azure portal can't be used at all during this process.

I am able to add a direct line channel to the bot az bot directline create ..., but I'm unable to add a trusted origin.

Describe the solution you'd like

I should be able to add a trusted origin using the Azure CLI or some REST API.

Describe alternatives you've considered

This must be done without the Azure portal, so I haven't been able to find any alternatives.

Additional context

• I'm hoping this functionality already exists and that someone can point me in the right direction.
• I created a Stack Overflow question asking for help related to this issue.

[stevengum]

Sorry for the delay, thanks for letting us know! I'll investigate this issue this week and see if it's doable. I'll update this ticket after I have an definite answer

[daveta]

@stevengum : Any updates?

[hcyang]

@stevengum : Any updates?

[stevengum]

It's in the Swagger spec and in the currently generated code in the azure-mgmt-botservice SDK, so I can add this feature in. 👍 I'll add the feature for Sprint 74.

[tsuwandy]

@stevengum, has this been added to Sprint 74?

[stevengum]

@tsuwandy that's correct; I'm planning on getting it in next week.

[stevengum]

@ericchansen, @CezaryMarcjan this is at risk for Sprint 74; when using the Azure CLI to create a new directline site, the new parameters --is-secure-site-enabled and --trusted-origins are passed along to the request and sent to the server but the response does not configure the appropriate settings using these two values.

I'm going to follow up with @swagatmishra2007 in the morning to see if we can figure this out quickly.

[stevengum]

Unfortunately we're blocked for this, and tentatively targeting the first week in October for getting the REST API up and running.

[stevengum]

I tested the code on Monday against a development environment and it all worked! 🎆

Still targeting the first week in October for code complete, and it would be released with the Sprint 75 timeframe of 10/15/2019.

After the ability to change the Direct Line configuration is live on the REST API, I'll update this thread so that @ericchansen is unblocked if he wishes to pursue using the REST API instead of waiting for Azure CLI 2.0.75.

[stevengum]

@ericchansen, the changes went live so you should be able to call the update API for Direct Line now.

Yesterday I tested the calling the API via a local branch of Azure CLI and it worked.

I'm planning on adding support for this API in the Azure CLI in either sprint 75 or sprint 76. (Azure CLI version 2.0.75 or 2.0.76)

[cwhitten]

@stevengum do you have an ETA on which sprint this will be landing in?