-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Use TestContainers for AWS Local Stack #19157
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
Open
hishamco
wants to merge
6
commits into
main
Choose a base branch
from
hishamco/aws-local-stack
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
2ec32b2
Use TestContainers for AWS Local Stack
hishamco 0cad839
Add integration tests to GitHub workflow
hishamco 82df941
Try to use latest image
hishamco a9abdb2
Revert "Try to use latest image"
hishamco 51e1c63
Run integration tests on linux only
hishamco bcbc8e6
Tweaks
hishamco File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
8 changes: 8 additions & 0 deletions
8
test/OrchardCore.Tests.Integration/AmazonS3/CommonCredentials.cs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,8 @@ | ||
| namespace OrchardCore.Tests.Integration.AmazonS3; | ||
|
|
||
| public static class CommonCredentials | ||
| { | ||
| public const string AwsAccessKey = "AKIAIOSFODNN7EXAMPLE"; | ||
|
|
||
| public const string AwsSecretKey = "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"; | ||
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
This PR looks good although @Piedone really wanted that we use S3Mock because it is lighter in size and executes faster. There is a Java version but no C# one on Testcontainers. Also, let's keep the integration_tests.yml file and nothing else, I don't think @Piedone will like it.
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.
When the build trigger, I didn't notice any delay
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.
That's 1min 55 seconds execution time added on every PR.
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.
Yep. This pulls in everything from AWS. We just need S3.
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 will check I remembered there's an option to specify the service, such as S3 for instance, but I need to make sure
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.
We can do that if and when we'll do that. No need to waste time until that uncertain future.
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.
This PR based on the meeting feedback, but you or Jasmin can discuss that as a topic in the upcoming meeting
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.
At this stage, this PR makes things worse in two ways, what Jasmin and I pointed out here. There's no need to discuss this at the meeting, especially not among the two of us, since we're in agreement. It's you who needs to reflect on the feedback.
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.
Don't get me wrong. I understand your feedback very well :) But it would be nice if @Skrypt mentioned the concern in the last meeting - to save the time -
Based on the discussion, @sebastienros suggested using TestContainers, which is why I submitted the PR, but not forcing acceptance of it
Uh oh!
There was an error while loading. Please reload this page.
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 could not raise a concern not knowing which Docker image is available from testcontainer. I asked questions in that meeting and I said I would try ; which is what you did here. Now, if that makes things worst now we know. Can't know without trying. Thanks for doing the work and saving me time. Now we know that we should'nt assume that testcontainer is better all the time.