feat(designer): Removing some hard coded built in operations in consumption and moving to backend api #6930
Conversation
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
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.
Type of Change
Current Behavior
Few built in AI operations are currently hard coded in Consumption search/manifest/connector service. Those are being moved to normal shared apis now and backend controller will serve them as part of these api calls.
New Behavior
Need to add isBuiltIn query parameter while fetching operation or operationManifest for these operations served by backend.
Impact of Change
There shouldn't be any change as such in the UI, backend api is not deployed anywhere to test it so wont merge it until then.
Test Plan
Just tested with mock data, no api available