Template Discoverability + Contribution

[jongio]

• [ ] https://github.com/Azure/azure-dev/issues/398
• [ ] https://github.com/Azure/azure-dev/issues/287
• [ ] https://github.com/Azure/azure-dev/issues/425

[karolz-ms]

Parts

• [x] Template discovery for the CLI
• [x] Template discovery in VS Code
• [x] Template discovery in GitHub.com
• [x] Template discovery from Docs
• [x] Template discovery from Samples Browser

Things to consider:

• Should we have a custom endpoint that encapsulates a list of templates + some auto-discovery logic?
• Or should that template discover logic be embedded in the CLI (e.g. look for GitHub templates belonging to some org(s) with some label(s)) and the VS Code should just leverage that logic in the CLI?

[jongio]

Ideally, we use github labels and query based on that label

[jongio]

We could create an 'awesome repo' that lists all repos, MS and community.

[markweitzel]

We should have the following for public preview:

• Template discovery for the CLI
• Template discovery in VS Code

[ellismg]

Ideally, we use github labels and query based on that label

FWIW - I would be a little hesitant to build something in the CLI itself that uses the GitHub API as the source of truth due to rate limiting from the GitHub side. We'd have to make anonymous requests and I've seen other tools that do this get hampered by rate limiting (for example, the bicep install script uses GitHub at the source of truth for the "latest" version and we had seen that fail in CI from time to time with rate limit issues)

[jongio]

Triage: We have template lists in cli and vs code, which is good enough for public preview.

[puicchan]

We have done some work here for cli, doc and in vs code. Adding @savannahostrowski for the uber template repo strategy.

[rajeshkamal5050]

@savannahostrowski closing since samples are now published to the Microsoft samples browser.