title | description | ms.custom | services | ms.service | ms.component | author | ms.author | ms.date | ms.topic | manager |
---|---|---|---|---|---|---|---|---|---|---|
include file |
include file |
include file |
azure-dev-spaces |
azure-dev-spaces |
azds-kubernetes |
ghogen |
ghogen |
05/11/2018 |
include |
douge |
- Hit F5 (or type
azds up
in the Terminal Window) to run the service. The service will automatically run in your newly selected spacedefault/scott
. - You can confirm that your service is running in its own space by running
azds list-up
again. First, you'll notice an instance ofmywebapi
is now running in thedefault/scott
space (the version running in thedefault
is still running but it is not listed). If you runazds list-uris
, you will notice that the access point URL forwebfrontend
is prefixed with the text "scott.s.". This URL is unique to thedefault/scott
space. The special URL signifies that requests sent to the "scott URL" will try to first route to services in thedefault/scott
space, but if that fails, they will fall back to services in thedefault
space.
Name DevSpace Type Updated Status
------------------------ -------- ------- ------- -------
mywebapi scott Service 3m ago Running
mywebapi-bb4f4ddd8-sbfcs scott Pod 3m ago Running
webfrontend default Service 26m ago Running
Uri Status
------------------------------------------------------------- ---------
http://localhost:53831 => mywebapi.scott:80 Tunneled
http://webfrontend.6364744826e042319629.canadaeast.aksapp.io/ Available
This built-in feature of Azure Dev Spaces lets you test code in a shared space without requiring each developer to re-create the full stack of services in their space. This routing requires your app code to forward propagation headers, as illustrated in the previous step of this guide.
To test your new version of mywebapi
with webfrontend
, open your browser to the public access point URL for webfrontend
and go to the About page. You should see your new message displayed.
Now, remove the "scott.s." part of the URL, and refresh the browser. You should see the old behavior (with the mywebapi
version running in default
).