-
Notifications
You must be signed in to change notification settings - Fork 902
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(lambda): available Runtimes shared between Deploy stage and Functions tab #10050
fix(lambda): available Runtimes shared between Deploy stage and Functions tab #10050
Conversation
…nctions infra tab
The following commits need their title changed:
Please format your commit title into the form:
This allows us to easily generate changelogs & determine semantic version numbers when cutting releases. You can read more about commit conventions here. |
@Mergifyio backport release-1.30.x release-1.31.x release-1.32.x |
❌ Command disallowed due to command restrictions in the Mergify configuration.
|
https://github.com/Mergifyio backport release-1.30.x release-1.31.x release-1.32.x |
✅ Backports have been created
|
…ions tab (spinnaker#10050) * Fix: Exporting availableRuntimes from the Stage definition for the Functions infra tab * Fixing formatting - prettier
Having the Lambda available Runtimes defined in 2 places creates a drift between what is available in the deploy stage vs what it is available for manual creation of a Lambda function through the Functions tab.