Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for ngrok in the build pipeline #66

Closed
cagdasdavulcu opened this issue Apr 22, 2019 · 2 comments
Closed

Add support for ngrok in the build pipeline #66

cagdasdavulcu opened this issue Apr 22, 2019 · 2 comments

Comments

@cagdasdavulcu
Copy link
Contributor

gulp ngrok-serve

cagdasdavulcu added a commit to cagdasdavulcu/generator-teams that referenced this issue Apr 22, 2019
@cagdasdavulcu
Copy link
Contributor Author

We can also design it to update messaging endpoint of bot channel registration via. gulp process and auto side loading of teams package in teams.

With current implementation are the following steps supported:

  • run ngrok
  • get url of ngrok tunnel
  • extract host name from url
  • set host name to process.env.HOSTNAME
  • generate manifest file
    ------> FEATURE: as next we can side load it in teams - we should design the teams access)
    ------> FEATURE: register the package in a teams channel
  • serve the express application
  • FEATURE: Change the bot channel registration in azure via. Azure AD App

Then we have no manual processes for debugging the teams application.

@wictorwilen wictorwilen added this to Backlog in Generator V2 Apr 23, 2019
@wictorwilen wictorwilen moved this from Backlog to In progress in Generator V2 Apr 23, 2019
@wictorwilen wictorwilen moved this from In progress to In review in Generator V2 Apr 27, 2019
@wictorwilen
Copy link
Member

Included in version 2.7.1 (7c45f92)

@wictorwilen wictorwilen moved this from In review to Done in Generator V2 May 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Generator V2
  
Done
Development

No branches or pull requests

2 participants