-
Notifications
You must be signed in to change notification settings - Fork 0
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
Filemanager: S3 events persistence #37
Conversation
brainstorm
commented
Jun 27, 2023
- Serializes S3 event attributes to DB backend.
- Using Axum (and AWS SDK) for local development, will transition to lambda Rust runtime crates later.
…ackled by native cloudwatch/cloudtrail
…inition... probably worth revisiting until we have traits well defined on the real app and we can add them in retrospective review
…) will come later on, first we run locally with Axum
Co-authored-by: Marko Malenic <mmalenic1@gmail.com>
Co-authored-by: Marko Malenic <mmalenic1@gmail.com>
…e event message struct
… migration / OrcaBus focus meeting' document
@mmalenic I was about to merge this gigantic PR but thought about getting your approval first. |
% ./deploy/aws-get-filemanager-logs.sh -c awslocal Parameter validation failed: Invalid length for parameter logGroupName, value: 0, valid min length: 1
…p because no lambda invoke has occurred yet? /cc @mmalenic
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, go for it.
In relation to the log groups, yes it fails if no events have been created yet. Maybe this needs a clearer note in the README.
More than a note: I meant that if a newcomer to the codebase reads the README, it should have the least amount of gotchas. Following the steps in sequence should yield a deterministic result and have a locally deployed dev setup as a result. |