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

Move AWS SPI code into Pekko repo #648

Merged
merged 12 commits into from
Jun 12, 2024
Merged

Move AWS SPI code into Pekko repo #648

merged 12 commits into from
Jun 12, 2024

Conversation

pjfanning
Copy link
Contributor

@pjfanning pjfanning commented May 8, 2024

@pjfanning pjfanning force-pushed the aws-api branch 3 times, most recently from e0adc7f to 4a93985 Compare May 8, 2024 14:39
@pjfanning
Copy link
Contributor Author

@mdedetrich I'm thinking of just removing the integration tests. They require real AWS access. There are unit tests that use testcontainers. I think those are enough. Is this ok?

@mdedetrich
Copy link
Contributor

mdedetrich commented May 8, 2024

@mdedetrich I'm thinking of just removing the integration tests. They require real AWS access. There are unit tests that use testcontainers. I think those are enough. Is this ok?

So we do actually have a real AWS account that is provided by Apache INFRA and it is currently being used by S3 integration tests and there is a github action that triggers it daily off the main branch (note that the reason this is run off the main branch is due to the fact that secrets are not available in pull requests).

Initially I would suggest trying to enable the tests and if its too much effort we can disable them, file an issue and try and we can try and re-enable them later. The reason I am suggesting this is that the core reason for me pushing for the AWS S3 integration tests is we did have an actual case of a regression that wasn't caught since initially there wasn't tests running against it.

@mdedetrich
Copy link
Contributor

mdedetrich commented May 9, 2024

Oh and I forgot to mention that if you do end up enabling integration tests, you have to work with Apache INFRA so that they can add in the necessary roles/permissions in the AWS account for whatever is being tested.

This does require some back and forth so given that it might make sense to do it in a different PR, but regardless I think we should still aim to have these tests in place

@mdedetrich
Copy link
Contributor

mdedetrich commented May 9, 2024

@pjfanning Is this ready?

@pjfanning
Copy link
Contributor Author

I'll leave the integration tests to another time but I have a couple of more things to do with this PR - it is pretty close now.

@pjfanning pjfanning changed the title [WIP] Move AWS SPI code into Pekko repo Move AWS SPI code into Pekko repo May 13, 2024
import software.amazon.awssdk.services.dynamodb.DynamoDbAsyncClient
import software.amazon.awssdk.services.dynamodb.model._

class ITTestDynamoDB
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems that IT and Test are usually placed at the end

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree, should be a post fix

@He-Pin
Copy link
Member

He-Pin commented May 14, 2024

I will take a look this weekend

build.sbt Outdated Show resolved Hide resolved
Copy link
Member

@samueleresca samueleresca left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good to me, Can someone else add their review?

@mdedetrich
Copy link
Contributor

This slipped off the table, will check it out tonight

@pjfanning
Copy link
Contributor Author

Would anyone have time to review this PR? I'm hoping to finalise the 1.1.0-M1 RC1 over the next week or so.

Copy link
Contributor

@nvollmar nvollmar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm
Just test naming should be fixed at some point

pjfanning and others added 5 commits June 11, 2024 11:18
Copy link
Member

@samueleresca samueleresca left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

already reviewed. I'm proceeding by approving.

Copy link
Contributor

@mdedetrich mdedetrich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, sorry for taking a while

@pjfanning pjfanning merged commit ed7ac36 into apache:main Jun 12, 2024
52 checks passed
@pjfanning pjfanning deleted the aws-api branch June 12, 2024 16:56
@pjfanning pjfanning restored the aws-api branch June 17, 2024 11:07
@pjfanning pjfanning deleted the aws-api branch June 17, 2024 11:08
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.

6 participants