Success story with resourceTypedParamsAndOutputs

[jikuja]

I just used resourceTypedParamsAndOutputs experimental feature to simplify our PoC template. Here is the diff of the relevant changes: jikuja/azure-data-factory-runtime-aci@security-1...jikuja:azure-data-factory-runtime-aci:bicep-resource-param-outputs

The only issue I encountered is the fact that secureValue: ir.listAuthKeys().authKey1 is valid code according to intellisense but bicep build will crash. Changing that code to listAuthKeys(ir.id, ir.apiVersion).authKey1 solved the issue.

Feelings: This is a cool feature addition for Bicep. Passing resources instead of resource id and usage of existing key word is too verbose.

---

Alternative approach: jikuja/azure-data-factory-runtime-aci@security-1...jikuja:azure-data-factory-runtime-aci:id-plust-list-functions

• Does not require experimental features
• On our use case requires passing more parameters into module

Feelings: Usage pattern documentation of list*() methods without resource accessor is really limited. I should have noticed this approach earlier.

[brwilkinson]

Thank you for sharing @jikuja I am very excited about this preview feature and how it can help to streamline code.

I will try to do a minimal repro of the issue that you mentioned then we can discuss some more.

[brwilkinson]

Okay I have the repro... @jeskew are you able to comment if this is expected behavior as a current limitation ?

Example1 - resourceTypedParamsAndOutputs - No Function?

param ir resource 'Microsoft.DataFactory/factories/integrationRuntimes@2018-06-01'
output authkeys object = ir.

Example2 - existing - Function

resource irexisting 'Microsoft.DataFactory/factories/integrationRuntimes@2018-06-01' existing = {
  name: ir.name
}
output authkeysexisting object = irexisting.

[jeskew]

This looks like a bug to me.

[brwilkinson]

Thank you @jeskew and also @jikuja for sharing and reporting.

Given this discussion is a show and tell, I will hope a separate issue to track, @jikuja I will tag you over there so you can follow.

[brwilkinson]

opened:

• Functions are not available when using resourceTypedParamsAndOutputs that are available on existing resource #10995

[brwilkinson]

new issue is:

• Instance functions on resource typed params and outputs crash the build and are not proposed as completions #10994