Support for CloudWatch Events as event source about kappa HOT 3 CLOSED

I'm interested in this feature too and may take a crack at it on my fork. I'll post an update here if I have something working if others want to help test it.

from kappa.

Got something working today. Does kappa own the event sources specified in the file? If so it seems odd to specify the arn in the yml file up front. I deviated slightly from the existing pattern in Context._create_event_sources() and introduced a notion of type - here's the example yaml:

---
name: kappa-cron
environments:
  dev:
    profile: xyz
    region: us-west-2
    event_sources:  
      - type: cloudwatch
        name: hello-cron-dev
        schedule: rate(1 minute)
        description: cron to run this lambda function every minute
        enabled: true
lambda:
  description: Kappa sample lambda that runs every minute
  handler: simple.handler
  runtime: python2.7
  memory_size: 128
  timeout: 3

The add() method does three things:

• events.put_rule
• lambda.add_permission
• events.put_targets

The assumption is that the rule is owned by kappa and can be removed if/when the lambda function is removed.

Any comments on the above? I could revert to the arn convention, but keeping things like the account id out of the yaml file seems good if we can avoid it.

The alternative would look like this (I removed some irrelevant sections for comparison):

---
name: kappa-cron
environments:
  dev:
    event_sources:  
      - arn: arn:aws:events:us-west-2:1234567890:rule/hello-cron-dev
        schedule: rate(1 minute)
        description: cron to run this lambda function every minute
        enabled: true

from kappa.

Ok - PR has been filed:

#69

from kappa.