Open nobuko-yamada opened 1 year ago
Hi @nobuko-yamada,
2.42.0 is not the latest Azure CLI(2.46.0).
Please upgrade to the latest Azure CLI version by following https://learn.microsoft.com/en-us/cli/azure/update-azure-cli.
Updated my CLI but still there is same message.
C:\Users\nobukoyamada>az --version
azure-cli 2.46.0
core 2.46.0
telemetry 1.0.8
Extensions:
logic 0.1.6
ssh 1.1.3
Dependencies:
msal 1.20.0
azure-mgmt-resource 21.1.0b1
Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\nobukoyamada\.azure\cliextensions'
Python (Windows) 3.10.10 (tags/v3.10.10:aad5f6a, Feb 7 2023, 17:05:00) [MSC v.1929 32 bit (Intel)]
Legal docs and information: aka.ms/AzureCliLegal
Your CLI is up-to-date.
I hope this information can be the help!
route to CXP team
@. Krishna @.> Logic Apps created from CLI are not using latest functions runtime of 4.X.
From: Yong Zhang @.> Sent: Wednesday, March 15, 2023 2:59 AM To: Azure/azure-cli @.> Cc: Arjun Chiddarwar @.>; Assign @.> Subject: Re: [Azure/azure-cli] "az logicapp create" doesn't support functions 4.x runtime (Issue #25820)
route to CXP team
- Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-cli%2Fissues%2F25820%23issuecomment-1469699098&data=05%7C01%7CArjun.Chiddarwar%40microsoft.com%7Cbb3d48252a5e43e06e1608db253bd9eb%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638144711219804492%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Ze%2BZQBFD5EthKWQEpuLqkL2Nmbhp%2FDeZTWbrK7vVHHM%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANPP7UGO7QY3RZWAV2HE5G3W4GHE5ANCNFSM6AAAAAAV3MCCTA&data=05%7C01%7CArjun.Chiddarwar%40microsoft.com%7Cbb3d48252a5e43e06e1608db253bd9eb%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638144711219804492%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dqSnzCMujk4PT3S0c%2BPwaD6yy%2FfPe1vI8zrOD%2FDi6W8%3D&reserved=0. You are receiving this because you were assigned.Message ID: @.***>
We are working on fix for this. Meanwhile please manually reset the version in the app settings under the "Configurations" blade from portal by setting this property to version ~4
"FUNCTIONS_EXTENSION_VERSION" : "~4"
manually reset the version in the app settings under the "Configurations" blade from portal by setting this property to version ~4 "FUNCTIONS_EXTENSION_VERSION" : "~4"
Thank you! Got it.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @antcp, @AzureAppServiceCLI.
Author: | nobuko-yamada |
---|---|
Assignees: | jiasli, archidda |
Labels: | `bug`, `Service Attention`, `App Services`, `Logic App`, `customer-reported`, `Installation`, `Client`, `Auto-Assign` |
Milestone: | Backlog |
Hi, @nobuko-yamada
A workaround is setting the v4 version after the az logicapp create
, like such:
az logicapp config appsettings set -n laName -g rgName --settings "FUNCTIONS_EXTENSION_VERSION=~v4"
Related command
Following this URL: https://learn.microsoft.com/ja-jp/cli/azure/logicapp?view=azure-cli-latest#az-logicapp-create az logicapp create --name --resource-group --storage-account e.g. az logicapp create --name mytestappsstd --resource-group playground --storage-account playground84c9 In this case, mytestappsstd is new Logic Apps Standard's name. playground and playground84c9 was my existing resource group and storage account.
Describe the bug
Deploy was succeed but some of configuration parameter is missing. ("Update to Functions 4.x runtime")
All of the parameter appeared first was below.
Because functions runtime is also 3, I changed manually by following this announcement. https://techcommunity.microsoft.com/t5/integrations-on-azure-blog/azure-logic-apps-standard-now-supports-azure-functions-v4/ba-p/3656072
To Reproduce
Run command. az logicapp create --name --resource-group --storage-account
In my case, my resource group was located at 'east asia'
Expected behavior
Configuration should be filled without maintaining manually for 4.x runtime.
Environment summary
Additional context
I'm support engineer in Japan. alias: nobukoyamada