Schedule event inputs are ignored

This is a Bug Report

Description

For bug reports:

• What went wrong? I added an events section to my function

  functions:
    produce:
      handler: produce.handler
      description: Blah blah.
      role: arn:aws:iam::...
      memorySize: 128
      vpc:
        securityGroupIds:
          - sg-12345
        subnetIds:
          - subnet-1
          - subnet-2
          - subnet-3
      events:
        - schedule: rate(1 minute)
          enabled: true
          name: update-schedule
          description: Updates the thing every minute
          input:
            bucket: my-bucket
            directory: some-directory
  

  A “rule” was created in AWS CloudWatch. But the inputs I defined were not in the rule.

• What did you expect should have happened? I expected the inputs to be in the “Constant (JSON text)” part of the CloudWatch rule

• What was the config you used? See above

• What stacktrace or error message from your provider did you see? I didn’t see any error, apart from the error in my lambda function because of the missing input.

Additional Data

• Serverless Framework Version you’re using: 1.16.1
• Operating System: My laptop runs MacOS, my lambda gets deployed by Codeship. My Codeship build runs on a docker image, based on lambci/lambda:build-nodejs
• Stack Trace: N/A
• Provider Error messages: N/A

[bartkummel]

Hi @pmuens , thanks for looking into this! I still have some comments:

• The example you linked to is a bit hidden. I was looking for an example with inputs. Although the example you linked to has inputs, the example is in a section on another topic. I think inputs deserve a section of their own, with a dedicated example. That would be a good improvement of the docs.
• Apparently, there are two different syntaxes of schedule: an “inline” variant, with only the rate, as well as a “full” variant, with all other options available. I think mentioning this explicitly would also improve the docs.
• I think it’s wrong that serverless doesn’t complain about the wrong indentation. It just fails silently by skipping the schedule. It would be better if there was at least a warning about a part of the YAML file being invalid. In my opinion serverless could also just exit with a proper error description on such an error.

[laurenfb]

Agreed that a warning on incorrect indentation would be super useful for this!