Skip to content

Port Cloud Adapter #3533

@joshgummersall

Description

@joshgummersall

This is the parent issue for all Cloud Adapter related issues. Tracking separate parity issues isn't very helpful when doing the initial port. Duplicate or related issues will be closed with a reference to this issue.

Checklist via #3728 (comment)

  • Locally with ngrok
    • HTTP(S) -> bot
      • Anonymous
      • AppId/Password
      • OAuth prompt
    • HTTP(S) -> parent -> to skill
      • Normal
        • Anonymous
        • AppId/Password for both parent and skill
      • Expect replies
        • Anonymous
        • AppId/Password for both parent and skill
    • Websocket -> bot
      • AppId/Password
    • Websocket -> parent -> skill
      • Normal
        • Not expect to work due to streaming skills limitations
      • Expect replies
        • AppId/Password
  • Azure web app
    • HTTP(S) -> bot
      • AppId/Password
    • HTTP(S) -> parent -> to skill
      • Normal
        • AppId/Password for both parent and skill
      • Expect replies
        • AppId/Password for both parent and skill
    • Named Pipes -> bot
      • AppId/Password
    • Named PIpes -> parent -> skill
      • Normal
        • Not expect to work due to streaming skills limitations
      • Expect replies
        • AppId/Password for both parent and skill
    • Websocket -> bot
      • AppId/Password
    • Websocket -> parent -> skill
      • Normal
        • Not expect to work due to streaming skills limitations
      • Expect replies
        • AppId/Password

Metadata

Metadata

Assignees

Labels

Area: SDKGeneral SDK issues that don't clearly map to other areas (e.g.: helper methods)P0Must Fix. Release-blockerSize: LThe issue is complex but it is well understood, it will take 4 to 8 days to complete

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions