search

apache / openwhisk

Apache OpenWhisk is an open source serverless cloud platform
https://openwhisk.apache.org/
Apache License 2.0
6.54k stars 1.17k forks source link

Epic: Tutorial and samples parity with Swift - Umbrella #282

Closed csantanapr closed 8 years ago

csantanapr commented 8 years ago

This is an umbrella issues to capture all the requirements/issues

This Swift actions need to be able to run on Swift 2.2 which is the current runtime supported in openwhisk

jberstler commented 8 years ago

@csantanapr we're going to need some details about what is currently in the Swift runtime. Language version, available frameworks, etc.

csantanapr commented 8 years ago

@bjustin-ibm Yep, what we have today is swift 2.2 is listed in the docs, and you get default frameworks.

@paulcastro is driving to move to swift 3 and have some frameworks pre-installed in the runtime, like a kitura components to be able to do http/networking, and any other one that we need to add for the samples

I think we can start working on the simple actions like greetings that don't require frameworks and will work on swift 2.2 or 3, to get a head start and give a chance for swift 3 to get it in.

rabbah commented 8 years ago

should take the opportunity to clean up the catalog and samples and rename some of those files as well (can you tell what is wcbin's purpose is - without looking at its code).

paulcastro commented 8 years ago

Just to confirm, as a stop-gap I'm looking into installing KituraNet as a framework to do network calls for Swift actions. I already have an image for Swift 3.

Hopefully, Foundation implementation will catch up soon.

csantanapr commented 8 years ago

@paulcastro the stop-gap is for swift 2? I think we should just go forward with Swift 3 if you already have it ready and not bother with Swift 2, team can use a docker image for develop the new swift actions

csantanapr commented 8 years ago

I think we should will skip github/webhook.swift for now. Since it's just a provider to setup the trigger to be invoke via webhook, and not an example the user will copy and modify to adjust to his need. What others think?

paulcastro commented 8 years ago

The stopgap requires Swift 3, but that version of Swift does not have stable APIs yet. I'd recommend keeping Swift 2 as our default and only moving to Swift 3 when it is stable. We can deploy Swift 3 as an experimental runtime.

csantanapr commented 8 years ago

Closing Epic, as children issues for Swift are done