Infrastructure: Remove Application Insights output and review dependencies
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- azure, python
- Domain
- cloud, infrastructure
Research direction
Start with infra/main.bicep and remove the specified Application Insights output, then inspect requirements.txt and the remaining template files for dependency versions and development-only configuration. Compare the repository with the referenced functions-quickstart-dotnet-azd PR; done means the output is absent, dependencies are reviewed, and hardcoded or development-only settings and secrets are not present.
Written by the indexing model from the issue text.
Description
🚨 Infrastructure and Best Practices Updates - Propagation from functions-quickstart-dotnet-azd PR #18
This issue tracks infrastructure and best practices changes that need to be applied to maintain consistency across Azure Functions AZD templates, based on PR #18 merged on August 7, 2025.
Required Changes
1. 🏗️ Remove Application Insights from Bicep Outputs
Remove this line from infra/main.bicep:
// REMOVE this line
output APPLICATIONINSIGHTS_CONNECTION_STRING string = monitoring.outputs.name
2. 📦 Update Python Package Dependencies (if applicable)
Review and update Python dependencies in requirements.txt to their latest stable versions:
# Update these to latest versions as appropriate
azure-functions
azure-functions-worker
3. 🔍 Review for Development-Only Configuration
Ensure no development-specific configuration is included in template files:
- Remove any hardcoded connection strings
- Remove development-only environment variables
- Ensure secrets are properly externalized
Impact
- Security: Removes exposed configuration from template
- Compatibility: Updates to latest stable versions
- Consistency: Aligns with current best practices across all Azure Functions AZD templates
Reference
- Source PR: https://github.com/Azure-Samples/functions-quickstart-dotnet-azd/pull/18
- Author: @nzthiago
- Scope: Part of batch propagation across 19 Azure Functions AZD templates
Related Language-Specific Templates
Similar infrastructure updates needed for all language variants:
- TypeScript templates (4 repositories)
- JavaScript templates (2 repositories)
- PowerShell templates (2 repositories)
- Java templates (1 repository)
/cc @nzthiago
- Dominant language
- Bicep
- Stars
- 30
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
bug needs-triage service/elbv2
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
hashicorp/terraform-provider-aws#50100 · 1 comment ·