-
Notifications
You must be signed in to change notification settings - Fork 906
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(lambdaStages): Exporting Lambda stages based on the feature flag setting #10085
Conversation
c95107a
to
2f3fe91
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not as comfortable with UI pieces, but this LOOKS like should fix the lambda issue
@mattgogerly would love your input on this since you did all the heavy lifting on the Lambda import :) |
https://github.com/Mergifyio backport release-1.34.x release-1.33.x release-1.32.x |
✅ Backports have been created
|
…settings (spinnaker#10085) (spinnaker#10091) Co-authored-by: Jason <jason.mcintosh@armory.io> Co-authored-by: ovidiupopa07 <105648914+ovidiupopa07@users.noreply.github.com> (cherry picked from commit 93bab65) Co-authored-by: Christos Arvanitis <christos.arvanitis@armory.io>
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