Outputs syntax about bicep HOT 8 CLOSED

What's the type of array items with this syntax?

// output with a value calculated by a loop (output copy loop in JSON):
output myLoopyOutput array = [for myItem in myArray {
  myProperty: myItem.myOtherProperty
}]

How to declare an output for resourceIds in sqlDatabases?

resource[] sqlDatabases 'Microsoft.DocumentDB/databaseAccounts/sqlDatabases@2020-03-01' [
    for dbindex in length(param.databaseName) {
        <db properties>
    }
]

from bicep.

With this proposal, output declarations may scatter in a .arm file, right?

from bicep.

Same as parameters - yup.

from bicep.

The other part I forgot to mention was that we brought up the idea of enforcing order in a file (inputs at the top, etc.) at our discussions with DevDiv folks and they felt it was better left up to the user and the auto formatter. The main reason given was that when a user is merging two files together by concatenating them together, nothing will compile until they fix the order.

from bicep.

Discussion notes from 7/1/2020 team meeting about outputs:

• Need to figure out if condition is actually useful on outputs. How do you consume a condition if it may not exist?
• Does secureString and secureObject type in outputs allow passing the value around?

from bicep.

We have consensus on minimal output declarations, but need to investigate secure types and conditions to commit to syntax for those.

from bicep.

Conditions on outputs and secure types on outputs are not that useful, so we will not support them in the bicep language. There is no remaining scenario that would require a modifier syntax for outputs. Therefore the proposal is reduced to the following:

// output value referencing a resource identifier
output myEndpoint string = myResource.properties.endpoint

// hard-coded output
output myHardcodedOutput int = 42

// output with a value calculated by a loop (output copy loop in JSON):
output myLoopyOutput array = [for myItem in myArray {
  myProperty: myItem.myOtherProperty
}]

As we appear to have team consensus on this syntax, I will send a spec pull request shortly and close this issue.

from bicep.

Created #67

from bicep.