Ping a specific public bundle in Logic App Standard by info.odysseyx@gmail.com October 18, 2024 written by info.odysseyx@gmail.com October 18, 2024 0 comment 1 views 1 background In some cases, you may need to use the same Logic App Standard bundle in different environments to ensure that the behavior of your workflows is the same. For example, I have a DEV, UAT and PROD environment and I want to keep the PROD environment so that it always uses the same bundle during development. Use default configuration (AzureFunctionsJobHost__extensionBundle__version = [1.*, 2.0.0) ), the backend will always upgrade to last bundle version which might cause unexpected behaviors across environments. In order to avoid this kind of issues, we can ping a specific public bundle for all the environments to maintain same behavior. Consideration Normally, we only need to modify AzureFunctionsJobHost__extensionBundle__version in environment variables to fallback to previous bundle version. But it is not a long-term resolution since old bundles might be removed from backend instances. So the following instruction introduce how to configure a public bundle as a special version for long-term usage. Configuration Steps 1. All the installed bundles can be found in Kudu: C:\Program Files (x86)\FuncExtensionBundles\Microsoft.Azure.Functions.ExtensionBundle.Workflows, we can check in workflow overview page for current using bundle version in lower environment (eg: dev, UAT) and download the specific bundle. 2. Once we have the bundle files, it will be better to use a special version number, for example 1.99.99, so we need to modify the version number in bundle.json (root folder of downloaded files). The sample content is following: {“id”:”Microsoft.Azure.Functions.ExtensionBundle.Workflows”,”version”:”1.99.99“} After the modification, compress all files as zip and be aware of that we don’t need root folder in zip. 3. To ping the bundle, we need to upload modified zip file into Logic App Standard file share (\home), if you don’t use private bundle before, you need to create path in Kudu like following: \home\data\Functions\ExtensionBundles\Microsoft.Azure.Functions.ExtensionBundle.Workflows\[version number (for example 1.99.99)]. You can then drag and drop the zip into Kudu and the files will automatically be unzipped and uploaded to a folder, which usually takes about 10 minutes. After uploading, your folder structure should look like this: 4. Change AzureFunctionsJobHost__extensionBundle__version In environment variables [1.*, 2.0.0) to the version you specified, rg: [1.99.99]. Logic App Standard will automatically restart when you apply the changes, and once the runtime reboots you can open any workflow to check the bundle version (in some cases a forced refresh is required to clear the cache using Ctrl+F5) . Source link Share 0 FacebookTwitterPinterestEmail info.odysseyx@gmail.com previous post Exploring the Power of Codespaces for Student Developers next post Announcing Public Preview of new attach/detach disks API for VMs/VMSS You may also like Lesson Learned #510: Using CProfiler to Analyze Python Call Performance in Support Scenarios October 18, 2024 Security review for Microsoft Edge version 130 October 18, 2024 New features for Azure Virtual Desktop for Azure Stack HCI October 18, 2024 How to Test Network on Linux Web App with Limited Tools October 18, 2024 Announcing Public Preview of new attach/detach disks API for VMs/VMSS October 18, 2024 Exploring the Power of Codespaces for Student Developers October 18, 2024 Leave a Comment Cancel Reply Save my name, email, and website in this browser for the next time I comment.