Add traces for `cloud` configuration values when restoring and publishing Bicep modules
Open
enhancement
tech debt
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 79
Description
This can be helpful when debugging issues like https://github.com/Azure/bicep/issues/13166.
Contributor guide
Research direction
Start by locating the code paths that restore and publish Bicep modules, then follow how their `cloud` configuration values are handled. Use issue #13166 as the debugging context and determine which trace output is needed; done means those values are visible when both operations run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100