Skip to content

fix(bicep): resolve conditional scope error in container registry module #232

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(bicep): resolve conditional scope error in container registry module #232

wants to merge 1 commit into from

Conversation

jjoek
Copy link

@jjoek jjoek commented Jun 27, 2025

Purpose

  • Fixes an issue where the scope for the containerRegistry module could not be resolved at compile time due to conditional logic.
  • Ensures that the scope is always explicitly defined using resourceGroup() or resourceGroup(containerRegistryResourceGroupName) to allow Bicep compilation to succeed.

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type

What kind of change does this Pull Request introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

  • Get the code
git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install
  • Test the code
This error occurs at compile time when you run `azd up`, where the error should look something like below: 
`BCP420: The scope could not be resolved at compile time because the supplied expression is ambiguous or too complex.`

After the above fix, this error should not occur anymore

What to Check

Confirm that azd up goes successfully without the above error

Other Information

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@jjoek