Alex Frankel

I believe we are getting close to getting this done and released as an experimental feature. @stephaniezyen / @polatengin can provide a more precise ETA.

I think this is also related to #7402. My guess is we are calling key vault for the `.getSecret()` function at the start of the deployment.

> > @ernestoak If you redeploy the template (with no changes) after seeing the `KeyVaultParameterReferenceNotFound` error, does the deployment succeed? I suspect this may be a consistency issue with Key...

The work is in our backlog, but not scheduled. The reality is we have way more open issues/feature requests then we'll ever be able to address. This means that the...

We are planning to add support for "deploy" settings in the bicep params file as per #7301: No ETA on when this will be implemented, but if that is where...

Agreed - ideally the command just becomes `az deploy -f foo.bicepparam` and everything needed is in that file. Or maybe even `az deploy` with a convention to look for something...

>However if you see the bicep params as the template consumer owned part and the main.bicep as the template provider then I would prefer to have a way to define...

You are right that `listKeys()` is firing too soon (though I wouldn't call this an idempotency issue). We are aware of the issue and plan to resolve it soon, but...

Linking an internal PR: https://msazure.visualstudio.com/One/_git/AzureUX-Deployments/pullrequest/7844064 We have started some work in the runtime to support dependsOn in the listKeys() as a new, optional argument in the listKeys() function. We will...

I got a note that the quota request was approved, so I am re-running the checks in US Gov