As a developer, I can use azd in Cloud Shell

[puicchan]

I should be able to run azd in cloud shell.

[jongio]

@danieljurek - Can you investigate what it would take for us to get azd in cloud shell?

Repo: https://github.com/Azure/CloudShell
Example: Azure/CloudShell#197

[danieljurek]

Addressed in Azure/CloudShell#248

[danieljurek]

Running in the context of CloudShell we may not have all tools installed for all possible deployments. Tools will need to be installed before running azd up etc.

Missing tools:

• SWA CLI
• JDK

todo-java-mongo

Error: todo-java-mongo

$ azd up 

ERROR: required external tools are missing:
 - need at least version 17.0.0 or later of Java JDK installed. Visit the website for your installed JDK to upgrade Java JDK version

todo-nodejs-mongo-terraform

(possible limitation of running deployments in parallel and exhausting disk space...)

Error:

Deploying service web...

ERROR: deploying service: packaging service web: failed to install project /home/daniel/test-failures/todo-nodejs-mongo-terraform/src/web, exit code: 228, stdout: , stderr: npm WARN config production Use `--omit=dev` instead.
npm WARN deprecated source-map-resolve@0.6.0: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN tar TAR_ENTRY_ERROR ENOSPC: no space left on device, write
npm WARN tar TAR_ENTRY_ERROR ENOSPC: no space left on device, write
npm ERR! code ENOSPC
npm ERR! syscall write
npm ERR! errno -28
npm ERR! nospc ENOSPC: no space left on device, write
npm ERR! nospc There appears to be insufficient space on your system to finish.
npm ERR! nospc Clear up some disk space and try again.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/daniel/.npm/_logs/2022-11-14T16_14_54_239Z-debug-0.log
: exit status 228
2022/11/14 16:15:09 failed to write file: write /home/daniel/.azd/telemetry/1231694720_itm.tmp: no space left on device

[danieljurek]

Issues discovered from testing:

• JDK version -- CloudShell: JDK version not high enough #1207
• Can't start docker service -- Cannot connect to the Docker in Cloud Shell #1206
• Unable to test user interactive login -- Unable to test user interactive login due to: Your device is required to be managed to access this resource #1029 -- this can be solved by supplying --subscription <subscription> to the azd up command

[danieljurek]

@savannahostrowski -- Issues discovered when running on CloudShell

[savannahostrowski]

Ah I see.

Okay, so I'd say re. JDK, we should try to see if the Cloudshell team can bump to 17. For the other issue, re. #1206, let me ping the Cosmos team and figure out what scenarios are most compelling to them.

[danieljurek]

Dependencies for releasing:

• We are waiting for release of an updated base image from CloudShell (DevOps issue)
• Arranging CSS support for CloudShell so customer issues can be routed

Other improvements:

• Authentication can be made more seamless (CloudShell Auth #1528)

[danieljurek]

Update. We tested a "workaround" for the JDK upgrade in a local CloudShell container image and the test succeeded.