-
Notifications
You must be signed in to change notification settings - Fork 89
bump aws sdk v2 to v3 #2254
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
SylvainSenechal
wants to merge
7
commits into
development/2.13
Choose a base branch
from
improvement/ZENKO-5054
base: development/2.13
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
bump aws sdk v2 to v3 #2254
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
0ab5d6f
bump zenko_tests from aws sdk v2 to v3
SylvainSenechal 0e5d500
bump ctst tests aws sdk to higher versions
SylvainSenechal ccaa825
migrate backbeat tests to aws sdk v3
SylvainSenechal acadea3
migrate cloudserver tests to aws sdk v3
SylvainSenechal 085d550
migrate node_tests client to aws sdk v3
SylvainSenechal b5553f5
migrate smoke_tests to aws sdk v3
SylvainSenechal 54ba63d
migrate iam_policies tests to aws sdk v3
SylvainSenechal 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 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
Large diffs are not rendered by default.
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
Oops, something went wrong.
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.
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.
Not sure if I should add a try catch to these functions. They are used for cleanup in before/after all tests
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.
IMO no. Why do you think you should ?
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.
Maybe its ok because these functions are just used for cleanup in after().
But if there are some errors without try catch, Im not sure the cleanup will be done properly