provide warning if there is a segment mismatch between type and name

[bmoore-msft]

Consider:

resource configScript 'Microsoft.Compute/virtualMachies/extensions@2020-06-01' = {
name: 'configScript'
location: location

Where we have a child resource, but a single segment in the name - we should be able to flag that at dev-time (certainly compile time)

[alex-frankel]

Hopefully once #272 is done, this becomes less of a concern

[anthony-c-martin]

Hopefully once #272 is done, this becomes less of a concern

I think this is technically out of scope (no pun intended) for the scope spec, but definitely something I'm interested in. Doing validation on a user-supplied string becomes tricky as soon as expressions become involved, and forcing users to format their own segmented strings feels unnecessarily burdensome.

The syntax I'm thinking about is something like the following:

resource mvVm 'Microsoft.Compute/virtualMachies@2020-06-01' = {
  name: 'myVm'
  ..whatever..
}
resource configScript 'Microsoft.Compute/virtualMachies/extensions@2020-06-01' = {
  parent: myVm
  name: 'configScript' // we just expect the child name, similar to the nested resource syntax in templates today
  ..whatever..
}

[bmoore-msft]

I don't know if I would introduce a new/non-arm way... scope makes some sense but I don't know if that's the way the platform will treat it (it might, we haven't done the work yet).

The parent property might be challenging because I may have more than one generation that I need to specify.

My guess is that the common pattern will be parameters or literals separated by slashes. Anything else would be more work. Catching that case would be easy - whether we need to catch any/all cases is probably worth more discussion.

[alex-frankel]

What does "non-arm" way mean here? What if we support this new property in the IL?

[anthony-c-martin]

Fixed with #1800