ayan.poddar/eShopOnContainers
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Updated 10.1 Using Azure Dev Spaces and AKS (markdown)

Eduard Tomàs 2019-04-11 14:52:38 +02:00
parent 5680ee1332
commit 0b7dc4b094
1 changed files with 27 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
10.1-Using-Azure-Dev-Spaces-and-AKS.md

@ -3,10 +3,36 @@ DRAFT STATE
Steps:
```
az extension add --name dev-spaces-preview
```
![image](https://user-images.githubusercontent.com/1712635/40263928-ec5f9c90-5ace-11e8-9476-539b5547c06d.png)
```
az aks use-dev-spaces -g your-aks-devspaces-resgrp -n YourAksDevSpacesCluster
```
![image](https://user-images.githubusercontent.com/1712635/40273317-028cc4ee-5b73-11e8-94ff-69959b23476b.png)
Once devspaces tooling is added, type `azds --version` to get the version of DevSpaces tooling.
Tested DevSpaces tooling version was:
```
Azure Dev Spaces CLI (Preview)
0.1.20190320.5
API v2.17
```
Future versions should work, unless they introduce _breaking changes_.
## Prepare environment for DevSpaces
From a Powershell console, go to `/src` folder and run `prepare-devspaces.ps1` (no parameters needed). This script will copy the `inf.yaml` and `app.yaml` files from `/k8s/helm` to all project folders. This is needed due to a limitation of devspaces tooling used. Note that the files copied are added in `.gitignore`.
## Deploy to a devspace
If you want to deploy a project to a specific devspace, just go to its source folder (where `.csproj` is) and type `azds up`. This will deploy the project to the current devspace.
Due to the status of devspaces today, _Web SPA_ do not use Dev Spaces (so, you can't deploy the SPA in devspace).