Skip to content
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

New-AzFunctionApp cmdlet should write a warning message when setting default values for parameters that are not provided #18192

Closed
Francisco-Gamino opened this issue May 17, 2022 · 2 comments
Closed

New-AzFunctionApp cmdlet should write a warning message when setting default values for parameters that are not provided #18192

Francisco-Gamino opened this issue May 17, 2022 · 2 comments
Assignees
@Francisco-Gamino
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Functions Service Attention This issue is responsible by Azure service team.
Milestone
May 2022 (2022-05...

Comments

@Francisco-Gamino
Copy link
Contributor

Francisco-Gamino commented May 17, 2022 •
edited
Loading

Description

New-AzFunctionApp cmdlet should write a warning message when setting default values for parameters that are not provided.

Previous verbose messages:

  1. RuntimeVersion not specified. Setting default runtime version for '$Runtime' to '$RuntimeVersion'

  2. FunctionsVersion not specified. Setting default FunctionsVersion to '$FunctionsVersion'

  3. OSType for $Runtime is '$OSType'

New warning messages:

  1. RuntimeVersion not specified. Setting default value to '< currentDefaultValue >'. This default value is subject to change over time. Please set this value explicitly to ensure the be behavior is not accidentally impacted by future changes.

  2. FunctionsVersion not specified. Setting default FunctionsVersion to '< currentDefaultValue >'. This default value is subject to change over time. Please set this value explicitly to ensure the be behavior is not accidentally impacted by future changes.

  3. OSType not specified. Setting default value to '< currentDefaultValue >'. This default value is subject to change over time. Please set this value explicitly to ensure the be behavior is not accidentally impacted by future changes.

Issue script & Debug output

N/A

Environment data

N/A

Module versions

N/A

Error output

N/A
@Francisco-Gamino Francisco-Gamino added bug This issue requires a change to an existing behavior in the product in order to be resolved. needs-triage This is a new issue that needs to be triaged to the appropriate team. labels May 17, 2022
@ghost ghost removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label May 17, 2022
@Francisco-Gamino Francisco-Gamino self-assigned this May 17, 2022
@Francisco-Gamino Francisco-Gamino mentioned this issue May 17, 2022
Closed
8 tasks
@dingmeng-xue dingmeng-xue added Service Attention This issue is responsible by Azure service team. Functions labels May 17, 2022
@ghost
Copy link

ghost commented May 17, 2022

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @ahmedelnably, @fabiocav.

Issue Details

Description

New-AzFunctionApp cmdlet should write a warning message when setting default values for parameters that are not provided.

Previous verbose messages:

  1. RuntimeVersion not specified. Setting default runtime version for '$Runtime' to '$RuntimeVersion'

  2. FunctionsVersion not specified. Setting default FunctionsVersion to '$FunctionsVersion'

  3. OSType for $Runtime is '$OSType'

New warning messages:

  1. RuntimeVersion not specified. Setting default value to '< currentDefaultValue >'. This default value is subject to change over time. Please set this value explicitly to ensure the be behavior is not accidentally impacted by future changes.

  2. FunctionsVersion not specified. Setting default FunctionsVersion to '< currentDefaultValue >'. This default value is subject to change over time. Please set this value explicitly to ensure the be behavior is not accidentally impacted by future changes.

  3. OSType not specified. Setting default value to '< currentDefaultValue >'. This default value is subject to change over time. Please set this value explicitly to ensure the be behavior is not accidentally impacted by future changes.

Issue script & Debug output

N/A

Environment data

N/A

Module versions

N/A

Error output

N/A
Author: Francisco-Gamino
Assignees: Francisco-Gamino
Labels:

Service Attention, Functions, bug
Milestone: May 2022 (2022-05-24)❗ Breaking change release ❗

@isra-fel
Copy link
Member

This is closed by #18193 #18195 and #18209

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Francisco-Gamino Francisco-Gamino

Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Functions Service Attention This issue is responsible by Azure service team.
Projects
None yet
Milestone
May 2022 (2022-05-24)❗ Breaking chang...
Development

No branches or pull requests
3 participants
@isra-fel @Francisco-Gamino @dingmeng-xue