-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding support for custom lambda scripts #10
Comments
What do you need to change in the transform lambda function contained in this repo? If you log your Lambda function to a Cloudwatch log group, then this existing terraform module should be able to be used as-is. You would push your changes to a branch you create in your own repo and then open a PR with that being the source and the destination being the master branch in this repo. |
I'd like to set source using the log group of the incoming event and switch to sending logs in json format among a couple other possibilities. Most of it is covered by the new lambda discussed here so I figured easies approach would be to allow swapping out of the lambda source file. As far as the approach, makes sense. I'll fork the repo and make my changes there. |
I'm working on some aws lambdas that we want to forward logging to splunk for. The only thing is we need to customize the transform lambda function script some. I've cloned the repo and made changes that should allow this, but I don't seem to be able to push the changes. Would you be able to give me permission to create a branch and push?
The text was updated successfully, but these errors were encountered: