nuclio

• Fix eventhub databinding after change in upstream amqp (#583)
• Special handling for docker hub in playground (support docker.io) (#578)
• Golang functions can implement InitContext, called once per context (#573)

Important: In this release, nuclio-sdk was renamed to nuclio-sdk-go (a non-backwards compatible change). If you upgrade to 0.2.5, make sure to update your imports to nuclio-sdk-go.

• nuctl has better support for -p, -f, --nuclio-src-x removed (#568)
• Travis configuration improvements - bails on failure (#569)
• if error is not wrapped, return the error as a cause (#561)
• Shell runner redacts sensitive logs (#558)
• Added v3io-go-http to list of packages required
• Update contribution guide following changes to repos (#556)
• Vendor nuclio/zap (#555)
• Better golang build log (#554)
• Extract logger, zap to repos; nuclio-sdk is now nuclio-sdk-go (#553)
• Support old style dockerconfig (#551)
• Support cron trigger in playground (#549)
• Playground: Allow generic form generation for key-value input (#542)

• Updated 'Further reading' with AKS (#1) (#546)
• Kubernetes documentation overhaul (#544)
• Playground recover from panic (#537)
• Support docker registry secret (#536)
• Re-enable processor web interface (#530)
• Added azure event hub example (#535)
• Added "Getting started guide" for Nuclio on Microsoft Azure AKS (#529)
• Add uniform stress test suite (#510)
• Playground reject simultaneous deploys (#526)
• Image-specific environment variables (#509)
• Point to nuctl releases rather than build from source (#515)
• Development of Azure Event Hub Trigger (#511)
• Align eventhub databinding field names with eventhub trigger (#512)
• Playground: make some Triggers fields optional (#508)
• Databinding refactoring, (basic) Azure event hub databinding added (#507)
• Fixed camel case keys being converted to lower case in processor configuration file (#506)
• Cron Trigger (#487)
• Adding support for deploying Nuclio on Azure AKS. (#505)

• Local platform invokes functions differently if initiator is dockerized or not (#503)
• First run build commands, then add files to images - better docker cache utilization (#482)
• Add "disableCache" in build configuration (#496)
• Playground uses platform invoker, kube invoker uses DNS (#502)
• Playground: reduce logo file size (#501)
• Playground: fix suggesting to create new function with existing name (#499)
• Playground: fix issue with keyboard nav on filtered function list (#498)
• Playground: Deleting trigger from UI does not actually delete trigger (#492)
• Playground refreshes docker credentials (#497)
• Added explicit error in Builder.getRuntimeName() when function path is a directory with function.yaml, which doesn't contain the runtime name (#489)
• Functions receive platform config - respect only metrics (#493)
• Playground: enforce all lowercase for function name (#491)
• Playground: wrap lines of "Commands" field (#490)
• Fixed issue where long(ish) bodies to Python functions would fail on subsequent invocations (#473)
• Playground: print logs on failed invocation, too (#472)
• Playground: Fix commands value not showing on loading a function (#471)
• Fix return response for Python 2.7 (#470)
• Playground: clear all fields on selecting a function (#469)
• Fix issue with updating "Commands" (and other arrays) on deploying (#468)
• Local platform respects configured HTTP port (#466)

• Javascript and NodeJS runtimes supported (#342)
• Users can specify response headers for shell functions invoking executables (#446)
• If function.yaml exists in directory or zip file - specifying runtime is not mandatory during build (#406)
• All temporary files are cleaned up after build (#405)
• Paths can be added to HTTP trigger in playground
• Playground allows JSON/numeric values for runtime key-value input
• Playground can invoke with binary file, download binary response, display img in log
• Remove unsafe from code (#277)
• Clearer errors when things go wrong (#402)

• Users can supply an archive (zip, tar.gz) containing function code / configuration (#375)
• Playground supports specifying PyPy, Python:2.7 and Python:3.6
• Playground supports the v3io-item-poller trigger
• Docker releated build errors should output reason as warn and info level logs, to be visible in the playground logs and non-verbose nuctl
• Python context.Response has default values for all fields. User can only provide non-default
• Minor build cleanup (#209)
• Processor build integration tests now share common base structure so that all runtimes run the same suite without code duplication
• Python handlers can return binary data (#218)
• Added experimental helm chart
• Fixed: nuctl get -o yaml/json (#422)
• Fixed: v3io databinding would fail type assertion, broken in 0.1.0
• Fixed: Golang compilation errors printed only once in logs
• Fixed: make did not properly build nuctl on non-linux

Major:

• Experimental pypy runtime - available in nuctl only (#327)
• Playground facelift (still WIP)
• Added shell processor (#280)

Minor:

• Playground cache is only 24H (#331)
• Documentation restructure
• Playground has more examples

Internal:

• Same function configuration structure used all across builder, processor, playground