Skip to content
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

Open
wants to merge 35 commits into
base: develop
Choose a base branch
from
Open

Conversation

ab295382
Copy link
Member

@ab295382 ab295382 commented Feb 17, 2025

Make sure you have checked all steps below.

Issue

Tests

  • My PR adds the following tests OR does not need testing for this extremely good reason:
    • MyUnitTest

Documentation

  • In case of new functionality, my PR adds documentation that describes how to use it, or I have linked to a
    separate issue for that below.
  • If I have added or removed any dependencies from the project, I have updated the NOTICES file.

@ab295382 ab295382 linked an issue Feb 17, 2025 that may be closed by this pull request
…d S3 and DynamoDB permissions to BulkExportStack
…Lambda for consistency and readability; add DynamoDB and S3 permissions to BulkExportStack
@ab295382 ab295382 marked this pull request as ready for review February 21, 2025 14:12
@ab295382 ab295382 requested review from kr565370 and patchwork01 and removed request for patchwork01 February 24, 2025 09:27
@ab295382 ab295382 requested a review from rtjd6554 February 24, 2025 09:28
* 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());
Copy link
Collaborator

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?

@@ -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
Copy link
Collaborator

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?

Copy link
Member Author

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

Copy link
Collaborator

@patchwork01 patchwork01 Feb 27, 2025

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.

Copy link
Member Author

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.

@ab295382 ab295382 removed the request for review from kr565370 February 26, 2025 11:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Create new CDK stack for Bulk Export
4 participants