You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Forgive me if I'm doing something wrong, but I've noticed a lot of our templates will fail to display the names correctly, even when parameters are provided. Turns out this seems to be because we use a lot of nested resources. It looks like the resource names are struggling to display when the resources are nested within a deployment resource. Is this a bug or am I using the extension incorrectly? When the resource is nested: When I move the resource to the root it's fine (but no longer linked to the parent):
Again, apologies if this is just me misunderstanding, but as far as I can see the names should resolve correctly?
Describe the bug
Forgive me if I'm doing something wrong, but I've noticed a lot of our templates will fail to display the names correctly, even when parameters are provided. Turns out this seems to be because we use a lot of nested resources. It looks like the resource names are struggling to display when the resources are nested within a deployment resource. Is this a bug or am I using the extension incorrectly?
When the resource is nested:
When I move the resource to the root it's fine (but no longer linked to the parent):
Again, apologies if this is just me misunderstanding, but as far as I can see the names should resolve correctly?
To Reproduce
The text was updated successfully, but these errors were encountered: