Alex Frankel

``` 'Resource type "Microsoft.KeyVault/vaults/keys@2019-09-01" does not have types available.' ``` Originally reported in Azure/bicep#1020

FYI the keyVault related issues should be resolved in the next 2-3 weeks.

I'm not convinced using VS Code auth is always the right choice/required. Seems like CLI auth is convenient if it's a tool I already use and am signed into, no?

Need to confirm the behavior Uche is describing. Need to also consider whether deploy should *only* support az account extension creds.

Plan is to get rid of the above 4 and replace with single "resource" snippet that fills in the following: ``` resource {name} '{provider/type}@{api-version}' = ``` With tab stops in...

Hi @ramkobos -- we definitely will implement this at some point, but don't have a precise ETA. Is this something you would be interested in submitting a PR for? If...

When you select "Deploy a bicep file" from the context menu (by right clicking in the editor window or on the bicep file itself), we will automatically select that bicep...

@ucheNkadiCode -- do have a task for documenting the bicep deploy feature? If so, we can track that issue to make this a bit clearer and probably close this one....

Can you share the full repro with the resource that is trying to use the `parent` property?

Can plan to use the symbolic name when that is implemented for ARM Template JSON