Support multiple calls to Push-OutputBinding to same `-Name`
See original GitHub issueCurrently, there is a limitation that if you want to push two items to the same storage queue, you must call Push-OutputBinding
only once with an array of those items. It’s more natural in the script to call Push-OutputBinding
multiple times at the time of creation of that queue item rather than collecting them and then pushing at the end.
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (9 by maintainers)
Top Results From Across the Web
PowerShell developer reference for Azure Functions
When the output binding accepts a collection of values, you can call Push-OutputBinding repeatedly to push multiple values.
Read more >Azure Functions | Using output binding multiple times
Whether you can call an output binding multiple times in a function depends on the binding type and how it is written.
Read more >PowerShell in Azure Functions v2 is generally available
When the output binding accepts a collection of values, you can call Push-OutputBinding repeatedly to push multiple values; When the output ...
Read more >Using PnP PowerShell in Azure Functions
Notice that the Azure Function scripts in this article run in a separate thread/job. ... -ManagedIdentity Get-PnPMicrosoft365Group Push-OutputBinding -Name ...
Read more >Custom Bindings for Azure Functions - Emanuel ... - YouTube
Push - OutputBinding 'Anything' - Custom Bindings for Azure Functions - Emanuel Palm - PSConfEU 2022 · PowerShell Conference EU · Managing Microsoft ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Agreed. We will have to play with them ourselves first anyways.
My personal opinion is: start conservatively – assuming no collection support for new out bindings.
Fixed via #168