Port ARM snippets to bicep - part 2

[bhsubra]

Port arm snippets - part 2

[MarcusFelling]

@anthony-c-martin @majastrz mind reviewing? Hoping to get this merged before publishing a contribution guide.

[anthony-c-martin]

I noticed a bug in requesting completions for the snippets - following is the repro. I was testing this with the res-keyvault-secret snippet but I suspect it applies to all of them:

1. Type res-kse. Instead of accepting the completion, press Esc to cancel the dialog.
2. Request completions again with Ctrl+Space. res-keyvault-secret is offered as an option.
3. Select res-keyvault-secret. The snippet is inserted, but the output is malformed:

   res-resource keyVault_keyVaultSecret 'Microsoft.KeyVault/vaults/secrets@2016-10-01' = {
     name: 'keyVault/keyVaultSecret'
     properties: {
       value: 'secretValue'
     }
   }

EDIT: I'll raise a bug for this, as I think it's unrelated to this set of changes.

[anthony-c-martin]

The symbolic name here is fixed, but it feels like customers will most likely want to change this. Should we offer a placeholder on the symbolic name?

[majastrz]

One challenge here is that it will make the authoring of the snippet bicep file harder because we'll get a parse error. However, my understanding was that we were going to have some sort of convention-based replacement. I see that the names of name placeholders do match the symbolic names, but I guess the logic to turn symbolic names into placeholders isn't there yet? @bhsubra?

---

In reply to: 611932375 [](ancestors = 611932375)

[bhsubra]

@majastrz , do you mean named placeholder for name E.g: ${name: logAnalyticsWorkspace}? We currently don't have that support, but I can try to add some logic to support the same.

[bhsubra]

I'll try to make this change in a follow up PR. Let me know if you have any concerns.

[anthony-c-martin]

Looks awesome! Thanks for doing this!