Add parent object and child array as outputs to all modules

[MariusStorhaug]

Description

Output values should return info about parents and children, allowing for outputs something like

• deployedResource.parent.resourceGroup.name
• deployedResource.parent.subscription.id
• deployedResource.fileShares[0].name

Suggestion on parent

output parent object = {
    'resourceGroup': resourceGroup()
    'subscription' : subscription()
    //'managementGroup' : managementGroup() // Depending on the scope
    //'tenant' : tenant()
}

Suggestion on children:

@description('A list of all the <childType> objects.')
output <childType> array = <mainResource>::<childResource>

[jontreynes]

I will go through discovery phase of which modules have this case

[jontreynes]

All cases (This will be a running list)

1. https://github.com/Azure/ResourceModules/blob/main/arm/Microsoft.AnalysisServices/servers/.bicep/nested_rbac.bicep

[jontreynes]

Notes from today add outputs in reference output example1 { }

server_rbac.output.example1

publicIPAddress: {

        id: !(empty(publicIPAddressId)) ? publicIPAddressId : publicIPAddress.outputs.publicIPAddressResourceId

      }

[jontreynes]

found all references to cases of lists generated by for loop by vscode regex searching with

"resource.*[for"

this gets the inventory of all cases that have dynamic array generated. Need to get inventory of hardcoded array as well

[jontreynes]

schedule a meeting with @MariusStorhaug for next week to review a sample of code to get feedback about using it across all bicep files

[AlexanderSehr]

As resources cannot be returned, I don't think this can be technically implemented right now. If I recall correctly, there exists an issue for that in the Bicep repo

[AlexanderSehr]

The capability to pass/return resources is on the roadmap to be implented in a future bicep version (scheduled to hit before Bicep Version 1.0 in summer). This must be supported before we can implement the feature.

[AlexanderSehr]

Unassigning as it has been a while and I don't expect @jontreynes to work on it any time soon. The required capability in Bicep is still not available.