The ScheduleEvent Input property now supports file paths

[GarrettBeatty]

The ScheduleEvent Input property now supports file paths (relative to… the project root or absolute) in addition to literal JSON strings. If the value resolves to an existing file, its contents are read and used as the input in the CloudFormation template.

Issue #, if available:

#2323 (comment)

Testing

manually tested by creating a program that looks like

[LambdaFunction(ResourceName = "ScheduledHandler", Policies = "AWSLambdaBasicExecutionRole", PackageType = LambdaPackageType.Image)]
[ScheduleEvent("rate(5 minutes)", ResourceName = "FiveMinuteSchedule", Description = "Runs every 5 minutes", Input = "schedule-input.json")]
public void HandleSchedule(ScheduledEvent evnt, ILambdaContext lambdaContext)
{
    lambdaContext.Logger.Log($"Scheduled event received at {evnt.Time}");
}
}

with json file like

{"action": "scheduled-processing", "source": "five-minute-rule"}

validated resulting template looks like

},
        "Events": {
          "FiveMinuteSchedule": {
            "Type": "Schedule",
            "Properties": {
              "Schedule": "rate(5 minutes)",
              "Description": "Runs every 5 minutes",
              "Input": "{\"action\": \"scheduled-processing\", \"source\": \"five-minute-rule\"}"
            }
          }
        }

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.