Are there any plans to allow for setting different messaging endpoints for deployment slots. Currently there doesnt seem to be a way to specify a different messaging endpoints.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
I'll enquire.
Is there any workaround to use slots with bots? So far, the only thing that worked for me was to deploy two different bot Web Apps and two different Bot Services.
I haven't had a chance to try this out, and we'll be moving away from using the .bot file in a few release cycles, but the following might work for you.
Review the information for how-to deploy. Then, update the .bot file to include an additional endpoint for each additional slot, such as:
{
"type": "endpoint",
"appId": "<app-id>",
"appPassword": "<app-password>",
"endpoint": "<hosted-endpoint-url>",
"name": "staging",
"id": "<unique-id>"
},
If you're working with a bot already on azure, you could edit the .bot file in place, or download and republish the bot.
@RealLucasMeyer I ended up just deploying a bot registeration app. Its essentially the bot connector without the bot. If you arent using premium channels no cost. Set the messaging endpoint to the slot url. So I have "Botname" which is full bot webapp. And not registration app "Botname-Dev" and "Botname-QA" with their messaging endpoints set to deplpyment slots Dev and QA
@JonathanFingold adding endpoints won't do anything. Only one endpoint is actually listening for messages. Adding extra endpoints is just so you have setting and keys if you want to switch them
Is there any update on this ticket? I'm exploring whether I can use slots or if I have to create a new bot app with different messaging endpoints.
@ImKator. I don't have any additional information yet. For additional help, you can post questions at Stack Overflow using the botframework tag.
We are planning a devops article that should address this question, but I don't have a schedule yet. Until then, you could ask our community support at Stack Overflow using the botframework tag.
@JonathanFingold do you have an updated timeline for that Dev Ops article?
Unfortunately no, other than not scheduled for the 4.5 release.
Most helpful comment
Unfortunately no, other than not scheduled for the 4.5 release.