Add telemetry for IO exceptions when discovering custom bicepconfig.json files
Open
enhancement
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 79
Description
Raised by https://github.com/Azure/bicep/pull/4576#discussion_r715884730.
Contributor guide
Research direction
Start with the discussion linked in the issue, especially the referenced pull request conversation, to identify how custom bicepconfig.json files are discovered and where IO exceptions occur. Done means telemetry is emitted for those IO exceptions; the issue does not name files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100