[draft] Template updates for codespaces

[danieljurek]

Attempting to set up environment using shell scripts

[azure-sdk]

Repoman Generation Results

Repoman pushed changes to remotes for the following projects:

Project: todo-csharp-cosmos-sql

Remote: azure-samples-staging

Branch: pr/902

You can initialize this project with:

azd init -t Azure-Samples/todo-csharp-cosmos-sql -b pr/902

View Changes | Compare Changes

---

Project: todo-csharp-sql

Remote: azure-samples-staging

Branch: pr/902

You can initialize this project with:

azd init -t Azure-Samples/todo-csharp-sql -b pr/902

View Changes | Compare Changes

---

Project: todo-java-mongo-aca

Remote: azure-samples-staging

Branch: pr/902

You can initialize this project with:

azd init -t Azure-Samples/todo-java-mongo-aca -b pr/902

View Changes | Compare Changes

---

Project: todo-java-mongo

Remote: azure-samples-staging

Branch: pr/902

You can initialize this project with:

azd init -t Azure-Samples/todo-java-mongo -b pr/902

View Changes | Compare Changes

---

Project: todo-nodejs-mongo-aca

Remote: azure-samples-staging

Branch: pr/902

You can initialize this project with:

azd init -t Azure-Samples/todo-nodejs-mongo-aca -b pr/902

View Changes | Compare Changes

---

Project: todo-nodejs-mongo-swa-func

Remote: azure-samples-staging

Branch: pr/902

You can initialize this project with:

azd init -t Azure-Samples/todo-nodejs-mongo-swa-func -b pr/902

View Changes | Compare Changes

---

Project: todo-nodejs-mongo

Remote: azure-samples-staging

Branch: pr/902

You can initialize this project with:

azd init -t Azure-Samples/todo-nodejs-mongo -b pr/902

View Changes | Compare Changes

---

Project: todo-nodejs-mongo-terraform

Remote: azure-samples-staging

Branch: pr/902

You can initialize this project with:

azd init -t Azure-Samples/todo-nodejs-mongo-terraform -b pr/902

View Changes | Compare Changes

---

Project: todo-python-mongo-aca

Remote: azure-samples-staging

Branch: pr/902

You can initialize this project with:

azd init -t Azure-Samples/todo-python-mongo-aca -b pr/902

View Changes | Compare Changes

---

Project: todo-python-mongo-swa-func

Remote: azure-samples-staging

Branch: pr/902

You can initialize this project with:

azd init -t Azure-Samples/todo-python-mongo-swa-func -b pr/902

View Changes | Compare Changes

---

Project: todo-python-mongo

Remote: azure-samples-staging

Branch: pr/902

You can initialize this project with:

azd init -t Azure-Samples/todo-python-mongo -b pr/902

View Changes | Compare Changes

---

Project: todo-python-mongo-terraform

Remote: azure-samples-staging

Branch: pr/902

You can initialize this project with:

azd init -t Azure-Samples/todo-python-mongo-terraform -b pr/902

View Changes | Compare Changes

---

[rajeshkamal5050]

This looks good overall - my main concern is that this is not a trivial amount of work and the changes need to happen within each template and is not generic to azd. Just thinking if there is some easier way to support codespaces better from an azd & vs code tooling perspective vs required template change.

If users are using our templates as a starting point great, but doesn't solve for the devify experience out of the box.

@danieljurek do we have issues for moving these from templates to azd and vscode/vs respectively. + @philliphoff

[danieljurek]

@wbreza , @rajeshkamal5050, @philliphoff -- I have opened a couple issues to track how we improve the debugging experience with vscode/codespaces

• https://github.com/Azure/azure-dev/issues/917
• https://github.com/Azure/azure-dev/issues/918

[danieljurek]

After walking through some more scenarios with @weikanglim, we should not take these shell scripts into main. They improve the "happy" path debug scenarios both in vscode (on desktop) and in codespaces... however, it's possible for configurations to become more complex (growing to multiple API services, switching to desktop vscode + codespaces + private API ports, etc.) where environment configuration scripts cannot detect and handle all scenarios.

To that end the next steps are:

• New PR with codespaces-only improvements (resizing the container memory requirements... maybe one or two other things)
• Keep this PR open, use as a demo branch for now to demonstrate where the happy debug path should lead in the presence of a more complete solution implemented with azd + vscode extension (+ possible other codespaces changes)