fix(lambdaStages): Exporting Lambda stages based on the feature flag setting (backport #10085) #10090
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
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
…settings (#10085) Co-authored-by: Jason <[email protected]> Co-authored-by: ovidiupopa07 <[email protected]> (cherry picked from commit 93bab65)
jasonmcintosh
approved these changes
Apr 25, 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.
When the Lambda Stages where backported from the plugin to Deck the register pipeline stages where not exported.
Also the NumberConcurrencyInput.tsx from the plugin is a duplicate of the NumberInput of Deck so removing it from the codebase
This is an automatic backport of pull request #10085 done by Mergify.