This PR restructure the template infra folders contents into their corresponding tool sub folder to support multiple IaC tools. The changes in this pr are:

• Moves common Bicep files into a new bicep sub folder under Templates/common/infra, Templates/todo/common/infra.

• Update todo/projects/*/repo.yaml to pull common infra from the the new bicep folder.

• Update Repoman to enable copy of a single file using the from syntax. This change ensures backward behavior compatibility.

• Rename repo.yaml inside (python-mongo, nodejs-mongo) projects to repo-bicep.yaml and azure.yaml to azure-bicep.yaml as foundation for Terraform support . This change was tested and repos were successfully generated using the expected file names (e.g azure/yaml in generated templates).

• Update Repoman list to support repo.yaml and repo-.yaml to ensure backward compatibility to repoman.yaml files.

• Add vscode debug support (launch.json, tasks.json) for repoman generation for local dev experience.

Note : This changes were tested in a fork with a working end to end environment including template generation pipelines.

• GitHub Template PR
• Azdo Repoman template generation CI
• Generated template-todo-python-mongo
• Generated template-todo-csharp-mongo

/azp run azure-dev - repoman

Azure Pipelines successfully started running 1 pipeline(s).

Repoman Generation Results

Repoman pushed changes to remotes for the following projects:

Project: todo-csharp-cosmos-sql

Remote: azure-samples

Branch: pr/437

You can initialize this project with:

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

View Changes | Compare Changes

---

Project: todo-csharp-mongo

Remote: azure-samples

Branch: pr/437

You can initialize this project with:

azd init -t Azure-Samples/todo-csharp-mongo -b pr/437

View Changes | Compare Changes

---

Project: todo-csharp-sql

Remote: azure-samples

Branch: pr/437

You can initialize this project with:

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

View Changes | Compare Changes

---

Project: todo-nodejs-mongo-aca

Remote: azure-samples

Branch: pr/437

You can initialize this project with:

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

View Changes | Compare Changes

---

Project: todo-nodejs-mongo-swa-func

Remote: azure-samples

Branch: pr/437

You can initialize this project with:

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

View Changes | Compare Changes

---

Project: todo-nodejs-mongo

Remote: azure-samples

Branch: pr/437

You can initialize this project with:

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

View Changes | Compare Changes

---

Project: todo-python-mongo-aca

Remote: azure-samples

Branch: pr/437

You can initialize this project with:

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

View Changes | Compare Changes

---

Project: todo-python-mongo-swa-func

Remote: azure-samples

Branch: pr/437

You can initialize this project with:

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

View Changes | Compare Changes

---

Project: todo-python-mongo

Remote: azure-samples

Branch: pr/437

You can initialize this project with:

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

View Changes | Compare Changes

---

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: /check-enforcer evaluate Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command: /check-enforcer override

I updated the PR to follow the new folder structure . Here is a link to a complete CI test from a copy of this branch on CSE Env . @jongio @wbreza please take a look when you get a chance.

merged upstream main, and resolved the conflicts. @jongio @wbreza PR is ready for review/merge