-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[FunctionApp] Updated stacks api json to add PowerShell on Linux in Functions #17678
[FunctionApp] Updated stacks api json to add PowerShell on Linux in Functions #17678
Conversation
cc: @Francisco-Gamino @AnatoliB @pragnagopa @gzuber Please review this PR. Thanks! |
}, | ||
"isPreview": false, | ||
"isDeprecated": false, | ||
"isHidden": false |
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.
We want this stack to be hidden until we roll out functions host changes to support linux consumption
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.
Please add stack as hidden. Also, need to add tests that check powershell stack
Hey @stefanushinardi I sent you a message about the tests, let me know if I can help out! 😄 |
@pragnagopa @gzuber Added that tests for powershell. Thanks @Hazhzeng to help fix the local setip |
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.
Looks good!
@stefanushinardi Are we ready to merge? |
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.
💯 Thanks @stefanushinardi
@qwordy yup, thanks! |
Description
The PR is to add Powershell on linux offerings #17657
Testing Guide
Verified that now the command does not throw validation error when deploying with Linux os type. And also verified creation of both consumption and elastic premium plan
sample command:
History Notes
[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.
This checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.