Mass s&r: iron-io -> kumokit

docs/README.md

@@ -6,7 +6,7 @@
 
 If you are a developer using IronFunctions through the API, this section is for you.
 
-* [Quickstart](https://github.com/iron-io/functions#quickstart)
+* [Quickstart](https://github.com/kumokit/functions#quickstart)
 * [Definitions](definitions.md)
 * [fn (CLI Tool)](/fn/README.md)
 * [Writing functions](writing.md)
@@ -14,7 +14,7 @@ If you are a developer using IronFunctions through the API, this section is for
 * [Function file (func.yaml)](function-file.md)
 * [Packaging functions](packaging.md)
 * [Open Function Format](function-format.md)
-* [API Reference](http://petstore.swagger.io/?url=https://raw.githubusercontent.com/iron-io/functions/master/docs/swagger.yml)
+* [API Reference](http://petstore.swagger.io/?url=https://raw.githubusercontent.com/kumokit/functions/master/docs/swagger.yml)
 * [Hot functions](hot-functions.md)
 
 ## For Operators

docs/hot-functions.md

@@ -19,7 +19,7 @@ input/output.
 
 ## Implementing a hot function
 
-In the [examples directory](https://github.com/iron-io/functions/blob/master/examples/hotfunctions/http/func.go), there is one simple implementation of a hot function
+In the [examples directory](https://github.com/kumokit/functions/blob/master/examples/hotfunctions/http/func.go), there is one simple implementation of a hot function
 which we are going to get in the details here.
 
 The basic cycle comprises three steps: read standard input up to a previosly

docs/lambda/environment.md

@@ -25,7 +25,7 @@ such assumptions, please rewrite it.
 * ImageMagick version [6.9.3][magickv] and nodejs [wrapper 6.9.3][magickwrapperv]
 * aws-sdk version [2.2.12][awsnodev]
 
-[iron/node]: https://github.com/iron-io/dockers/blob/master/node/Dockerfile
+[iron/node]: https://github.com/kumokit/dockers/blob/master/node/Dockerfile
 [magickv]: https://pkgs.alpinelinux.org/package/main/x86_64/imagemagick
 [magickwrapperv]: https://www.npmjs.com/package/imagemagick
 [awsnodev]: https://aws.amazon.com/sdk-for-node-js/

docs/lambda/getting-started.md

@@ -3,7 +3,7 @@
 This guide will walk you through creating and testing a simple Lambda function.
 
 We need the the `fn` tool for the rest of this guide. You can install it
-by following [these instructions](https://github.com/iron-io/function/fn).
+by following [these instructions](https://github.com/kumokit/function/fn).
 
 *For this getting started we are assuming you already have working lambda function code available, if not head to the [import instructions] (import.md) and skip the next section.*
 

docs/lambda/import.md

@@ -1,7 +1,7 @@
 Import existing AWS Lambda functions
 ====================================
 
-The [fn](https://github.com/iron-io/functions/fn/) tool includes a set of
+The [fn](https://github.com/kumokit/functions/fn/) tool includes a set of
 commands to act on Lambda functions. Most of these are described in
 [getting-started](./getting-started.md). One more subcommand is `aws-import`.
 

docs/operating/extending.md

@@ -14,8 +14,8 @@ Listeners are the main way to extend IronFunctions.
 
 The following listener types are supported:
 
-* App Listeners - [GoDoc](https://godoc.org/github.com/iron-io/functions/api/server#AppListener)
-* Runner Listeners - [GoDoc](https://godoc.org/github.com/iron-io/functions/api/server#RunnerListener)
+* App Listeners - [GoDoc](https://godoc.org/github.com/kumokit/functions/api/server#AppListener)
+* Runner Listeners - [GoDoc](https://godoc.org/github.com/kumokit/functions/api/server#RunnerListener)
 
 ### Creating a Listener
 
@@ -29,8 +29,8 @@ package main
 import (
     "context"
 
-    "github.com/iron-io/functions/api/server"
-    "github.com/iron-io/functions/api/models"
+    "github.com/kumokit/functions/api/server"
+    "github.com/kumokit/functions/api/models"
 )
 
 type myCustomListener struct{}

docs/operating/metrics.md

@@ -21,5 +21,5 @@ TODO: List all metrics we emit to logs.
 
 ## Statsd
 
-The [Logspout Statsd Adapter](https://github.com/iron-io/logspout-statsd) adapter can parse the log metrics and forward
+The [Logspout Statsd Adapter](https://github.com/kumokit/logspout-statsd) adapter can parse the log metrics and forward
 them to any statsd server.

docs/operating/production.md

@@ -15,7 +15,7 @@ Here's a rough diagram of what a production deployment looks like:
 
 Any load balancer will work, put every instance of IronFunctions that you run behind the load balancer.
 
-**Note**: We will work on a smart load balancer that can direct traffic in a smarter way. See [#151](https://github.com/iron-io/functions/issues/151).
+**Note**: We will work on a smart load balancer that can direct traffic in a smarter way. See [#151](https://github.com/kumokit/functions/issues/151).
 
 ## Database
 
@@ -33,7 +33,7 @@ The message queue is pluggable and we currently support a few options that can b
 ## Logging, Metrics and Monitoring
 
 Logging is a particularly important part of IronFunctions. It not only emits logs, but metrics are also emitted to the logs. Ops teams can then decide how they want
-to use the logs and metrics without us prescribing a particular technology. For instance, you can [logspout-statsd](https://github.com/iron-io/logspout-statsd) to capture metrics
+to use the logs and metrics without us prescribing a particular technology. For instance, you can [logspout-statsd](https://github.com/kumokit/logspout-statsd) to capture metrics
 from the logs and forward them to statsd.
 
 [More about Metrics](metrics.md)

docs/operating/ui.md

@@ -6,4 +6,4 @@
 docker run --rm -it --link functions:api -p 4000:4000 -e "API_URL=http://api:8080" iron/functions-ui
 ```
 
-For more information, see:  https://github.com/iron-io/functions-ui
+For more information, see:  https://github.com/kumokit/functions-ui

docs/swagger.yml

@@ -532,7 +532,7 @@ definitions:
       payload:
         type: string
         # 256k
-        # maxLength breaks ruby generator too: https://github.com/iron-io/worker_ruby/blob/0aa9236ce5060af3f15758937712973f80dd54fe/lib/iron_titan/models/task.rb#L272
+        # maxLength breaks ruby generator too: https://github.com/kumokit/worker_ruby/blob/0aa9236ce5060af3f15758937712973f80dd54fe/lib/iron_titan/models/task.rb#L272
         # maxLength: 268435456
         description: Payload for the task. This is what you pass into each task to make it do something.
 

docs/writing.md

@@ -4,8 +4,8 @@ This will give you the basic overview of writing base level functions. You can a
 abstractions that make it easier such as [lambda](lambda/README.md).
 
 Also, for complete examples in various languages, see the [examples directory](/examples).
-We have language libraries for [Go](https://github.com/iron-io/functions_go), [Javascript](https://github.com/iron-io/functions_js) and
-[Ruby](https://github.com/iron-io/functions_ruby).
+We have language libraries for [Go](https://github.com/kumokit/functions_go), [Javascript](https://github.com/kumokit/functions_js) and
+[Ruby](https://github.com/kumokit/functions_ruby).
 
 ## Code