Skip to content

Show warning message for runtimes reaching end-of-life during publish #4241

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.

Sign up for GitHub

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

Jump to bottom
Open
MadhuraBharadwaj-MSFT opened this issue Jan 27, 2025 · 3 comments · May be fixed by #4324 or #4357
Open

Show warning message for runtimes reaching end-of-life during publish #4241

MadhuraBharadwaj-MSFT opened this issue Jan 27, 2025 · 3 comments · May be fixed by #4324 or #4357
Assignees
@umangsriv
Labels
enhancement

Comments

@MadhuraBharadwaj-MSFT
Copy link

MadhuraBharadwaj-MSFT commented Jan 27, 2025 •
edited
Loading

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.

Image

Image

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:

  1. 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)

  1. Compare against EOL dates in StacksAPI: See this
@fabiocav
Copy link
Member

Reaching out to @MadhuraBharadwaj-MSFT to make sure we have the information needed to triage and assign this issue.

@fabiocav
Copy link
Member

One of the questions in addition to what I'm gathering:

@MadhuraBharadwaj-MSFT , can you share the exact verbiage you want for the two conditions mentioned above? The one in the screenshot doesn't seem accurate (the date returned by the stacks API is the EOL date, instead of deprecation), so I want to make sure I have the one you would like to use.

Thanks!

@MadhuraBharadwaj-MSFT
Copy link
Author

MadhuraBharadwaj-MSFT commented Feb 19, 2025 •
edited
Loading

@fabiocav - we want to use the date returned by StacksAPI ie., the EOL date. The verbiage is in the table below

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'/language runtime> <latest available functions/stack version> as <current functions/stack 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'/language runtime> <latest available functions/stack version> as <current functions/stack runtime version> will reach end-of-life on and will no longer be supported. Learn more: aka.ms/FunctionsStackUpgrade"

Example 1: Publish action on a Node.js 18 App which is approaching end of life in April 2025 should show this warning message,
" Upgrade to Node.js 22 as Node.js 18 will reach end-of-life on April 30 2025 and will no longer be supported. Learn more: aka.ms/FunctionsStackUpgrade"

Example 2: Publish action on a Python 3.8 App which has reached end of life in October 2024 should show this warning message,
" Upgrade to Python 3.11 as Python 3.8 has reached end-of-life on October 07 2024 and is no longer supported. Learn more: aka.ms/FunctionsStackUpgrade"

Here's a link to the Core Tools API reference for this command: https://learn.microsoft.com/en-us/azure/azure-functions/functions-core-tools-reference?tabs=v2#func-azure-functionapp-publish

@fabiocav fabiocav assigned umangsriv and unassigned fabiocav Mar 5, 2025
@umangsriv umangsriv linked a pull request Mar 24, 2025 that will close this issue
Open
5 tasks
@umangsriv umangsriv linked a pull request Apr 10, 2025 that will close this issue
Open
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@umangsriv umangsriv

Labels
enhancement
Projects
None yet
Milestone
No milestone
3 participants
@fabiocav @MadhuraBharadwaj-MSFT @umangsriv