fix: s3ParamNotFound into ssmParameterNotFound #229
Merged
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
leszek-rozkiewicz
previously approved these changes
Oct 8, 2024
PiotrWaluszek
previously approved these changes
Oct 8, 2024
tcharewicz
previously approved these changes
Oct 9, 2024
Kolodziejczykmaciek
dismissed stale reviews from tcharewicz, PiotrWaluszek, and leszek-rozkiewicz
via
041a79c
Kolodziejczykmaciek
force-pushed
the
fix/ssm-type-err-check
branch
from
09b4b1b
to
041a79c
Compare
leszek-rozkiewicz
approved these changes
Oct 9, 2024
tcharewicz
approved these changes
Oct 9, 2024
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.
Requestor/Issue: Bug reported
Risk (low/med/high): low
Tested (yes/no): no
Description/Why: It is a bug that occurred during update to aws-sdk go v2. We need to check not s3 param not found but ssm parameter not found.