Introduce new API to resolve ComponentMetadata
#1229
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
slinkydeveloper
force-pushed
the
issues/1218
branch
from
356c786
to
fe1b1db
Compare
Merged
…ta). `ComponentMetadataResolver#resolve_latest_component_handler` will replace key extraction from now on, and will be used by invoker and ingress to build the `ServiceInvocation` struct.
slinkydeveloper
force-pushed
the
issues/1218
branch
from
fe1b1db
to
0bce9b0
Compare
igalshilman
approved these changes
Feb 28, 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.
Fix #1218
ComponentMetadataResolver#resolve_latest_component_handlerwill replace key extraction from now on, and will be used by invoker and ingress to build theServiceInvocationstruct.