-
Notifications
You must be signed in to change notification settings - Fork 11
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
CDK Stack for Bulk Export #4273
base: develop
Are you sure you want to change the base?
Conversation
…d S3 and DynamoDB permissions to BulkExportStack
…Lambda for consistency and readability; add DynamoDB and S3 permissions to BulkExportStack
…ortStack and SqsQueues
…ew properties for splitter queue and DLQ
...bulk-export-lambda/src/main/java/sleeper/bulkexport/lambda/SqsBulkExportProcessorLambda.java
Outdated
Show resolved
Hide resolved
...xport/bulk-export-lambda/src/main/java/sleeper/bulkexport/lambda/SqsBulkExportProcessor.java
Outdated
Show resolved
Hide resolved
...bulk-export-lambda/src/main/java/sleeper/bulkexport/lambda/SqsBulkExportProcessorLambda.java
Show resolved
Hide resolved
...bulk-export-lambda/src/main/java/sleeper/bulkexport/lambda/SqsBulkExportProcessorLambda.java
Show resolved
Hide resolved
...bulk-export-lambda/src/main/java/sleeper/bulkexport/lambda/SqsBulkExportProcessorLambda.java
Show resolved
Hide resolved
...bulk-export-lambda/src/main/java/sleeper/bulkexport/lambda/SqsBulkExportProcessorLambda.java
Outdated
Show resolved
Hide resolved
java/cdk/src/main/java/sleeper/cdk/stack/bulkexport/BulkExportStack.java
Show resolved
Hide resolved
* to their own SQS queue can give the role permission to write to their queue | ||
*/ | ||
IRole role = Objects.requireNonNull(lambda.getRole()); | ||
instanceProperties.set(CdkDefinedInstanceProperty.BULK_EXPORT_PROCESSOR_LAMBDA_ROLE, role.getRoleName()); |
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.
I'm not sure this is the role you would need to give permission to write to an output queue. The actual bulk export will be done in a longer running task, rather than in this lambda. Are you expecting the results will come back to the lambda somehow, or will they be published from the long running task?
java/core/src/main/java/sleeper/core/properties/instance/BulkExportProperty.java
Outdated
Show resolved
Hide resolved
java/core/src/main/java/sleeper/core/properties/instance/BulkExportProperty.java
Outdated
Show resolved
Hide resolved
@@ -254,6 +254,53 @@ public interface CdkDefinedInstanceProperty extends InstanceProperty { | |||
.description("The ARN of the dead letter queue used when leaf partition querying sleeper.") | |||
.propertyGroup(InstancePropertyGroup.QUERY) | |||
.build(); | |||
// Bulk Export |
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.
These properties are a bit misleading. There's a lambda that's called the bulk export processor lambda, but it's doing the splitting. There's no lambda called the bulk export splitter lambda. Do you want to adjust the names?
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.
I have added new properties for the splitter. The queues have been renamed to make it clearer
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.
It looks like these property names are still the same? The ones in BulkExportProperty have changed, but not in CdkDefinedInstanceProperty.
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.
There are BULK_EXPORT_SPLITTER_* properties as well as BULK_EXPORT_PROCESSOR_*. The latter are to be used in a new lambda (in the next ticket) that will run the actually export.
Make sure you have checked all steps below.
Issue
PR"
Tests
Documentation
separate issue for that below.