feat(ci): use localstack v3 provider for s3 #1948
Draft
Conversation
This file contains 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
peusebiu
force-pushed
the
localstack_s3_v3
branch
from
70ac7f6
to
e78af8d
Compare
Codecov Report
@@ Coverage Diff @@
## main #1948 +/- ##
=======================================
Coverage 91.97% 91.97%
=======================================
Files 164 164
Lines 27657 27657
=======================================
+ Hits 25437 25438 +1
+ Misses 1645 1644 -1
Partials 575 575 see 2 files with indirect coverage changes 📣 Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today! |
peusebiu
force-pushed
the
localstack_s3_v3
branch
2 times, most recently
from
4318a11
to
544c589
Compare
Signed-off-by: Petu Eusebiu <peusebiu@cisco.com>
peusebiu
force-pushed
the
localstack_s3_v3
branch
from
544c589
to
dc868fe
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What type of PR is this?
Which issue does this PR fix:
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs showing the issue:
Testing done on this change:
Automation added to e2e:
Will this break upgrades or downgrades?
Does this PR introduce any user-facing change?:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.