Description
Description
| Action: Deploying to an Existing Function App | Condition | Behavior | Warning message. |
|---|---|---|---|
| Command: func azure functionapp publish 'MyFunctionApp' | Functions version and/or stack version is out of support | Show warning message. | "Upgrade to Functions/Stack version as <stack/functions runtime version> has reached end-of-life on and is no longer supported. Learn more: aka.ms/FunctionsStackUpgrade" |
| Command: func azure functionapp publish 'MyFunctionApp' | Functions version and/or stack version will be out of support in less than 6 months | Show warning message. | "Use Functions/Stack version as <stack/functions runtime version> will reach end-of-life on and will no longer be supported. Learn more: aka.ms/FunctionsStackUpgrade" |
Current Behavior:
Running command func azure functionapp publish to deploy to a Node.js 18 App (as an example) does not warn the user of its upcoming EOL.
Acceptance Criteria:
Work item can be marked 'Completed' when we have implemented, tested and deployed the logic to show the above mentioned warning message when a user runs the command func azure functionapp publish , where is configured with a stack runtime version that has a) reached its end-of-life date, or b) will reach its end-of-life date in <6months.
Additional information:
- Getting current stack version information: See this
For Linux:
All stacks - get app runtime version from linux_fx_version (from site config)
For Windows:
Node: WEBSITE_NODE_DEFAULT_VERSION (from app setting)
.NET: netFrameworkVersion (from site config)
Java: javaVersion (from site config)
PowerShell: powerShellVersion (from site config)
- Compare against EOL dates in StacksAPI: See this