I've been working on adding Swift Support to Azure Functions. The framework supports the most popular triggers and bindings like Http, Queue, Table, Blob & Service Bus. More bindings/triggers support will be added soon! Swift Azure Functions are deployable to been tested on Azure.
https://github.com/SalehAlbuga/azure-functions-swift
Despite being in an early stage, It's a fully functioning Serverless Swift project that supports a major cloud provider! Here is a getting started guid Writing an Azure Function, in Swift! | by Saleh | Medium
Any feedback is more than welcome! 
21 Likes
Wow, this looks really cool. Thanks for putting this together. I've gotta try this after the holidays 
.
Oh, and one more thing, I see you're using grpc-swift 1.0.0-alpha-X which is really awesome. If you don't mind, it'd be much appreciated if you could write about your experience with it in the SSWG gRPC proposal thread: [Discussion] gRPC Swift
1 Like
@johannesweiss please let me know if you tried using Azure Functions for Swift 
I'd love to hear feedback on it!
1 Like
@Helge_Hess1 Thank you for the feedback! Can you please provide me with the version of macOS you're using? Also I just want to confirm that Function Core Tools are installed
You can install them from homebrew as well
brew tap azure/functions
brew install azure-functions-core-tools
I'm thinking of adding it as a dependency, but there are other ways to install the Core Tools, like from NPM, so I didn't wanna mess the version the user is using or cause conflicts
Glad it worked! For the TERM message, I have not seen it while testing before. I do provide that to func host start to retain the output format and colors. Can you please provide with more info about the environment? Are you running it from the macOS Terminal app or another terminal? I've tried in Terminal & VSCode Terminal but didn't get the message. Also I'm going to test locally without setting TERM.
For the Azure Functions Core Tools installation requirement, I'm going to check the homebrew dependencies config It would be nice to save a step from the prerequisites!
For the .NET Core SDK, I've added the Extensions Bundle to the function projects created by swiftfunc so it shouldn't be required anymore. I'll update the docs. The root permissions issue, has an open issue on Github, did you get it while installating from Homebrew?
@Helge_Hess1 I tried to repro the message you got about TERM, but I didn't have it in any of the shells. Interestingly, TERM is set to the same value you have. I'm testing the effect of removing it from code and it doesn't seem to affect it so far. Btw, I'm curious, have you got the same message again after a restart or in a new terminal window/session? I'm glad it worked for you!
UPDATE: I was able to repro the message you got with the latest V2 Core Tools. I've updated the Swift Functions CLI now with the fix Please update to the latest version. Also I filed a Github issue with the solution on the repo for reference!
I will need to try it out, since I wrote about the managed version of Apache OpenWhisk project with Swift in details in the Serverless Swift book by Apress https://www.apress.com/us/book/9781484258354 . I will let you know about porting my examples to Azure as well!
1 Like
In terminal run the following to create a new project:
swiftfunc init myFunctionsProj
If you’re used to using Functions Core Tools, Swift Function Tools are pretty similar. The init command we ran above is similar to that of the Core Tools, but it's going to create a Swift Functions Project! You're going to get the follow folder structure:
The project is basically a SwiftPM project with a couple of extra files for the purpose of Azure Functions framework.
The functions folder is going to be the home of your Functions!
1 Like
Exactly!
There are 4 dependencies. They seem reasonable to me given an azure function can serve http traffic.
dependencies: [
// Dependencies declare other packages that this package depends on.
.package(url: "https://github.com/vapor/vapor.git", from: "4.8.0"),
.package(url: "https://github.com/Flight-School/AnyCodable", from: "0.2.3"),
.package(url: "https://github.com/grpc/grpc-swift", .exact("1.0.0-alpha.12")),
.package(url: "https://github.com/JohnSundell/Files", from: "4.1.1"),
.package(url: "https://github.com/stencilproject/Stencil.git", from: "0.13.1"),
],
@Helge_Hess1 You're right, thank you for the feedback. Let me explain the dependencies.
First, Azure Functions provide 2 ways to support languages/runtimes. gRPC & HTTP (initially only gRPC but later HTTP Custom Handlers were introduced). This framework currently supports both. There are differences in writing an Azure Function in each approach.
Second, I used Vapor just to get things wired as this framework was one of the very first to support Azure Functions Custom Handlers when they were in preview.
I'm working to switch to SwiftNIO instead of Vapor for the HTTP worker (SwiftNIO is already used by grpc-swift).
This framework along with its CLI, supports all major Azure Functions deployment methods possible, in container or zip package deployment. In addition to testing locally on Linux or macOS.
I will provide updates here on my progress on SwiftNIO switch
Hey @Helge_Hess1I'm using Files & Stencil for codegen, to generate files & directories required by Azure Functions. Currently part of the codegen needs to be done in the worker itself. It's on my todo to move the codegen to the CLI tool along with using SPMDestinations, it will definitely save time & steps!
I'm actually interested in contributing to such a builder to deploy to both Azure & AWS, since both support HTTP traffic for requests! It think it will be very nice for the community
I'm using Files & Stencil for codegen
Soto for AWS uses Stencil for code generation.
1 Like
Yes azure-functions-swift-tools is the CLI tool package (to create project, functions, run locally, etc..).
There are a couple of ways to decouple infra code from the actual runtime, I'm thinking to explore moving as much as possible to the CLI tool.
Oh .NET installation is Not required! That was addressed a long time ago. Azure Functions have BundleExtensions that custom runtimes can use to bypass the .NET Core SDK installation and this worker utilizes them! Since the main post is not editable now, here is the updated getting started guide Azure Functions in Swift: From Code to Azure - DEV Community.
A lot has changed since the initial release!
One of goals of this framework is to make it as simple and as straightforward as possible for Swift devs to write Azure Functions without needing to think so much about the Azure Functions runtime (apart from the triggers, bindings and hosting of course)
1 Like