Releases: Azure/azure-functions-host
Functions 0.6.10462 (1.0.0-beta1-10462)
Few minor fixes for the previous release. Fixes include:
- ServiceBus Topic trigger portal invoke fix (#585)
- Fixing compilation warning for $return output bindings
Functions 0.6.10453 (1.0.0-beta1-10453)
Main things in this release are called out below.
- Enabling function timeouts (#18)
- Default execution timeout of 5 minutes is enforced. If a function runs longer than that it will be terminated.
- timeout is only enforced on Dynamic SKUs
- timeout can be configured via
functionTimeout
property inhost.json
- Imposing some naming restrictions on function names + binding names (#15). See Renaming a Function for instructions on renaming if you have a name that doesn't match the new rules.
- Support for function return bindings (#675)
- naming an output binding $return maps it to the function return value
- for C#/F#/Node, this allows simpler, more idiomatic code to be written (i.e. no
out
/byref
parameters required)
- Allow Node.js functions to return Promises (#158)
- Moved to Node.js version 6.5.0
- EventHub Consumer group fix (#570)
- Binding fixes for ManualTrigger (#628)
- lots of additional bug fixes
Functions 0.5.10398 (1.0.0-beta1-10398)
Main things in this release are called out below.
- New F# programming model! (Breaking)
- F# is now first class like C#, no longer using an out of proc execution model
- New Twilio output binding allowing you to easily send Twilio SMS messages from your functions!
- HttpTrigger binding improvements
- Moved to Node.js 6.4.0
- C# Package Restore improvements (addresses #312 #469)
- We now identify when a restore needs to be run and do it automatically
- Tracing Changes + Throttling
- File logging (which drives the Portal logs via log streaming) is now only enabled during Portal sessions
- If the Portal hasn't connected in 15 minutes, file logging is turned off. For historical logs, use the Dashboard view
- In addition, we now throttle tracing to a maximum of 250 lines per second
- Addresses issues #557 and #100
- Allow EventHub receiver options to be configured via host.json
- You can now add an
eventHub
config section and configure valuesmaxBatchSize
andprefetchCount
- See here for details
- You can now add an
- Improvements to multi-instance logging (addresses #164)
- Allow File Watch directories to be configured
- Fixed ManualTrigger input (addresses #602)
- Normalized
context.bindingData
property casing (addresses #426) (Breaking)- casing is now normalized to camel case
- Lots of other bug fixes
Functions 0.4.10355 (1.0.0-beta1-10355)
Main things in this release are called out below.
- timer trigger fixes to prevent duplicate executions and other schedule issues
- Added a blob lease based "primary host" detection mechanism to unblock a fix for #164
- For scaled out Function Apps (i.e. multiple instances), only one instance will acquire (and maintain) the blob lease
- Some logs and other actions will only be performed by the primary host
- Moving to latest minor versions of all our dependencies
- changed log file name format to make them more easily sortable (e.g. 2016-08-15T17-59-25Z-b84490e99a.log)
- Several other bug fixes
Functions 0.4.10341 (1.0.0-beta1-10341)
Hotfix release made to fix a bug with Function monitoring/metrics.
This hotfix contains a single commit: b903c91
Functions 0.4.10312 (1.0.0-beta1-10312)
Hotfix release made to fix a bug with the Mobile Apps binding.
This hotfix contains a single commit to consume the updated extension package: 512f2d4
Functions 0.4.10307 (1.0.0-beta1-10307)
Main things in this release are called out below. You can also review the raw commits since the last release.
- Lots of bug fixes (See the issues we closed out in this milestone)
- Function Exclusion : added the ability to exclude functions via new function level “excluded” metadata property
- set the
excluded: true
function metadata property to have the host completely ignore a function and not load it. It will not be invokable, even via the portal - this differs from the existing
disabled: true
function property, which tells the host to load the function, just not automatically trigger it, and only make it accessible via the portal (not regular requests)
- set the
- Changes to
rand-guid
binding parameter (Breaking)- previously you would use
%rand-guid%
(e.g. in a blob pathmycontainer/%rand-guid%
) - syntax has changed to
{rand-guid}
(e.g. in a blob pathmycontainer/{rand-guid}
)
- previously you would use
- Support for multiple Function exports
- added a new function level metadata property
entryPoint
which allows a function to explicitly declare its entry point - if a function has multiple named exports and no
entryPoint
property is specified, and there is an export namedrun
by convention, it is used. If there is only a single named export, it is used. - e.g. this allows a Node function to export multiple functions to aid in testability
- similarly, for C# the function code can include multiple functions (same logic as above)
- added a new function level metadata property
- Large refactoring of the binding pipeline for extensibility
Functions 0.3.10261 (v1.0.0-alpha1-10261)
Main things in this release are called out below. You can also review the raw commits since the last release.
- New Binding Extensibility Model
- Large refactor of all existing bindings to simplify extensibility
- All existing extensions now onboarded to runtime in “one line”
- (Breaking) New PowerShell execution model
- In proc model for PowerShell
- New SendGrid Email binding (including templates for C# and Node)
- Samples for C#/Node/PowerShell are in the repo (e.g. SendGrid Node Sample)
- EventHub Consumer Group support
- allow Consumer Group to be specified in function binding metadata (“consumerGroup”)
- flow this to EventProcessorHost
- DocDB/MobileTable parameter binding fixes
- support parameter binding on various binding properties
- Adding Microsoft.Azure.ApiHub.Sdk to shared assemblies – Allow users to easily #r in their C# Functions
- Misc. bug fixes
v1.0.0-alpha1-10238
v1.0.0-alpha1-10216
Hotfix release made to fix a bug that was introduced (#393). You can also review the raw commits since the last release.