Can using 'br:…' reference a published targetScope = 'local' artifact for bicep local-deploy?

[walr-nathan-driscoll]

I'm trying to use bicep local-deploy against a .bicepparam file whose using clause points at a Bicep artifact published to ACR with targetScope = 'local'. It fails with The referenced .bicep file must have targetScope set to 'local'.

I'd like to confirm whether this pattern is supported, or whether the supported pattern is to use a local wrapper .bicep (with targetScope = 'local') that consumes the published artifact via module 'br:…'.

Bicep CLI version: 0.42.1.51946 (per the embedded _generator metadata in the published artifact)
alerts-prod-weu.bicepparam:

using 'br:<my-acr>.azurecr.io/monitoring-dotnet-container-app-dynamic:latest'

param containerAppName = '...'
param resourceGroup    = '...'
param serviceName      = '...'
param env              = 'prod'

I recieve the following error: The referenced .bicep file must have targetScope set to 'local'.

[cookesan]

Based on the current local-deploy code and tests, the safe supported shape looks like: local .bicepparam -> local entrypoint .bicep with targetScope = 'local', and then that entrypoint can consume modules/extensions.

LocalDeployCommand.cs loads the semantic model from the .bicepparam using target and rejects the run unless that directly referenced .bicep has targetScope == local. The local-deploy docs and integration tests I found are all in that form (main.bicepparam using main.bicep).

So for your case, I would treat the local wrapper pattern as the supported one today: keep a local targetScope = 'local' entrypoint .bicep, and have that file reference the published artifact/module. I don't see a documented or tested direct .bicepparam -> using 'br:...' local-deploy path in the current source.

[walr-nathan-driscoll]

It appears that the local wrapper is not an option as well 🫤, as there is no scope for local() when referencing the module in the private registry. @cookesan thanks for your help.