fix: Don't assume that all service bindings existed before #2405
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.
Background
I changed
model.expectShape
tomodel.getShape
to so that the code doesn't fail if a given service is not present in the old model which can happen in certain cases.This is a fix for
software.amazon.smithy.model.node.ExpectationNotMetException: Shape not found in model: a.b#c
that occurs when a new service is being added that references an already existing operation which was also changed in some way.Full stacktrace:
Testing
I minimized the issue and then reproduced it in the unit test.
Links
SigV4Migration
was introduced in #2245By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.