search

Azure / pcs-cli

A CLI for deploying Azure IoT PCS
MIT License
33 stars 37 forks source link

Problems deploying Remote Monitoring via the CLI #503

Closed jenniferburch closed 5 years ago

jenniferburch commented 5 years ago

Type of issue

Description

Deployment of remote monitoring solution from source CLI is not producing a usable Remote Monitoring Solution

Steps to reproduce

  1. npm install -g iot-solutions
  2. pcs login
  3. pcs -t remotemonitoring -s basic -r dotnet
  4. Answer prompts, create DEP1 (this deployment works as expected)
  5. Forked https://github.com/Azure/pcs-cli to another repo and clone
  6. cd to the root folder
  7. npm install
  8. npm start
  9. npm link
  10. pcs login
  11. pcs -t remotemonitoring -s basic -r dotnet
  12. Answer prompts, create DEP2, use same values as DEP1 except for solution name

Expected behavior

Be able to launch the Remote Monitoring website

Current behavior <!-- The actual behavior observed --

Launch the remote monitoring website, it doesn't advance past the login screen, I get to the account picker, select the same account I published with, if first time enter password, then it goes back to the Pick an account, repeat

Known workarounds

...

Possible solution

...

Context and Environment

ppathan commented 5 years ago

@elvinm This is because of code in master default is pointing to a branch which isn't ready for release. Once we do the release this should be fixed automatically.

jenniferburch commented 5 years ago

Thanks @ppathan, so what branch represents the current release? Do you have an ETA on the next release?

elvinm commented 5 years ago

The latest release is out. The current (3.0.1) CLI release is now producing proper deployments.