Add Functions Timer trigger templates for Python, JavaScript, TypeScript, PowerShell, and Java#844
Add Functions Timer trigger templates for Python, JavaScript, TypeScript, PowerShell, and Java#844
Conversation
…Shell, and Java Agent-Logs-Url: https://github.com/Azure/awesome-azd/sessions/4fb013cc-3fa6-438b-9fed-a4ebbc3ba0c0 Co-authored-by: hemarina <104857065+hemarina@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Adds the remaining Azure Functions Timer trigger quickstart templates to the Awesome AZD gallery, aligning with the existing Azure Functions quickstart pattern and enabling discovery across multiple languages.
Changes:
- Added 5 new Azure Functions Timer trigger template entries (Python, JavaScript, TypeScript, PowerShell, Java).
- Tagged templates as Microsoft-authored with Flex Consumption deployment-related Azure service tags and Bicep IaC.
| "title": "Azure Functions Python Timer Trigger using Azure Developer CLI", | ||
| "description": "This repository contains an Azure Functions Timer trigger quickstart written in Python and deployed to Azure Functions Flex Consumption using the Azure Developer CLI (azd). The sample uses managed identity and a virtual network to make sure deployment is secure by default.", | ||
| "preview": "./templates/images/test.png", | ||
| "authorUrl": "https://github.com/Azure-Samples", | ||
| "author": "Azure Functions Team", | ||
| "source": "https://github.com/Azure-Samples/functions-quickstart-python-azd-timer", |
There was a problem hiding this comment.
These entries are tagged as Microsoft-authored ("msft"). Per the repo’s template review guidelines, please include a link to a test pipeline run or other proof (e.g., screenshots/logs) showing that each of these templates successfully deploys with azd up.
There was a problem hiding this comment.
@im-samz Could you provide proof of test run for these templates?
jongio
left a comment
There was a problem hiding this comment.
5 timer-trigger templates following the existing .NET pattern. Tag validation passes (all defined in tags.tsx, correct placement), all source repos exist and are public, UUIDs are unique, tests pass (336/336).
Two items before this can merge:
- Merge conflicts - this PR conflicts with main and needs a rebase.
- Deployment proof - these are msft-tagged templates. @hemarina can you provide a test pipeline link or screenshots showing each template deploys successfully with
azd up?
Minor: the descriptions say "make sure deployment is secure by default" and reference "azd" (lowercase), while the existing .NET timer template uses "ensure it's secure by default" and "AZD" (uppercase). Not blocking, but worth aligning for consistency.
| "title": "Azure Functions Python Timer Trigger using Azure Developer CLI", | ||
| "description": "This repository contains an Azure Functions Timer trigger quickstart written in Python and deployed to Azure Functions Flex Consumption using the Azure Developer CLI (azd). The sample uses managed identity and a virtual network to make sure deployment is secure by default.", | ||
| "preview": "./templates/images/test.png", | ||
| "authorUrl": "https://github.com/Azure-Samples", | ||
| "author": "Azure Functions Team", | ||
| "source": "https://github.com/Azure-Samples/functions-quickstart-python-azd-timer", |
There was a problem hiding this comment.
@hemarina These are msft-tagged templates. Per repo guidelines, please provide a test pipeline link or proof of successful deployment for each of these 5 timer templates.
Follow-up to #839 — adds the remaining Azure Functions Timer trigger quickstart templates across all supported languages.
Templates added to
templates.jsonfunctions-quickstart-python-azd-timerfunctions-quickstart-javascript-azd-timerfunctions-quickstart-typescript-azd-timerfunctions-quickstart-powershell-azd-timerfunctions-quickstart-java-azd-timerAll entries follow the existing .NET timer template pattern: Microsoft-authored, Flex Consumption deployment, Bicep IaC, with
functions,managedidentity,vnets, andappinsightsas Azure services. PowerShell usespowershellintags(notlanguages) consistent with other PowerShell templates since it's defined astype: "Tools"intags.tsx.