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

Open
wants to merge 11 commits into
base: main
Choose a base branch
from
Open

Conversation

pjfanning
Copy link
Contributor

@pjfanning pjfanning commented May 8, 2024

@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 and others added 8 commits May 13, 2024 22:23
@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

@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

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.

None yet

5 participants