I have some jobs running under an Azure Batch and I received a warning saying I must upgrade the API verion.
Where should I do that?
The current version I'm using will be removed on 10/31/2020
Edit:
I accessed my batch and then the Job Schedules:
These are the properties of one of those jobs:
Should I configure the api-version here?
Most likely, you are utilizing Batch through an SDK, Azure CLI, Powershell, or Batch Explorer. Each of these ultimately call the Batch service through a REST API which is versioned. You need to ensure that you are not using a deprecated version of such SDKs or tooling.
Please see this article for more information for associated SDK versions for deprecated REST API versions.
Related
Client browser session, on the web channel, displays deprecated dialogs and functionality in recently deployed version. The issue is resolved once cache is purged, am I missing a step or setting in deployment?
I'm using nodeJS SDK4.4 using Kudu for Azure deployment.
Thanks
I've never used Kudu specifically to deploy to the bot framework; the MSBF supports using the AZ CLI to deploy (though this seems to be similar enough, in that it is a "zip deployment"). That being said, it's possible the Kudu deployment method is somehow being delayed.
One option you could try is to enable continuous deployment through Github. It's as simple as authorizing Azure to look at the github repo you have your bot code in.
The Bot Framework has a how-to here.
I have created an Azure Function to store messages from Azure IoT Hub to Table Storage using built endpoint of EventHub of IoT Hub. I am using Azure Functions v2(.Net Standard) for creating the EventHubTrigger functions.I developed the function and tested it locally and it is working as required. But when I am hosting this function in Azure, it shows the following error in the portal:
Error: The binding type(s) 'eventHubTrigger' are not registered. Please ensure the type is correct and the binding extension is installed.
I have already installed the Microsoft.Azure.WebJobs.Extensions.EventHubs -v 3.0.0-beta4 nuget package in the code.
Can someone help with this error as nothing much is mentioned regarding this in the docs.
Following are the packages installed in the solution:
Microsoft.NET.Sdk.Functions 1.0.13
Microsoft.Azure.WebJobs.EventHubs 3.0.0-beta4
NETStandard.Library v2.0.3
The different behavior is caused by old Azure Functions and Web Jobs Tools in VS, which means VS still consumes old function templates and cli.
Just update VS2017 to latest version(15.8.6 right now) and go to VS menus>Tools>Extensions and Updates, find Azure Functions and Web Jobs Tools, update it to latest version(15.10.2009.0 right now).
After steps of update, new EventHub trigger template works with Microsoft.NET.Sdk.Functions 1.0.22 and Microsoft.Azure.WebJobs.EventHubs 3.0.0. And the function cli is
Azure Functions Core Tools (2.0.3)
Function Runtime Version: 2.0.12115.0
I have an existing webjob (.NET 4.6.1) that runs fine and gets triggered whenever a message arrives in a queue. I'm investigating how to migrate some applications to .NET Core 1.0 and as part of that I did some research.
It looks like at this point in time, .NET Core 1.0 only supports webjobs that run on a schedule and have no special Webjob features, such as this example: https://blog.kloud.com.au/2016/06/08/azure-webjobs-with-dotnet-core-rc2/
To have a queue message trigger the job I need the features of the Webjob packages. When I add any of the WebJobs Nuget packages (including beta versions), I get the error:
Package Microsoft.Azure.WebJobs.Core 2.0.0-beta2 is not compatible with netcoreapp1.0 (.NETCoreApp,Version=v1.0). Package Microsoft.Azure.WebJobs.Core 2.0.0-beta2 supports: net45 (.NETFramework,Version=v4.5)
One or more packages are incompatible with .NETCoreApp,Version=v1.0.
I did apply a workaround for the Azure Storage already as described in:
https://jeremiedevillard.wordpress.com/2016/09/27/use-the-azure-storage-library-in-netcore-application/
but thas apparently does not solve the issue for the Webjob package.
I am aware of some workaround of deploying a non-.NET Core webjob next to a .NET Core website as described here: How do I deploy an Azure WebJob alongside a .NET Core Web App via Git?
but - although that would work - I just want to know if I can port my webjob to .NET Core 1.
Does anyone know a way to do this?
TIA,
Jeroen
Since there's no push/notify mechanism built in Azure Storage Queues, it's still polling.
You could just poll the queue every X seconds and check for new messages. That's what the SDK is doing anyway, but in a civilized, elegant way. Nothing wrong with doing that.
From: https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-azure-and-service-bus-queues-compared-contrasted
Azure Storage Queues
Push-style API: No
Service Bus Queues
Push-style API: Yes
OnMessage and OnMessage sessions .NET API.
As far as I know, Azure WebJobs that use of WebJobs SDK in .NET Core is not supported currently. The following is the snipped from the davidebbo mentioned. More details info please refer to the issue.
To clarify, Azure WebJobs that use .NET Core work fine. It's specifically the use of the WebJobs SDK that is not yet supported.
Is there a way to keep Diagnostics 1.0 but upgrade to Azure SDK 2.5?
We use very simple diagnostics that just writes into Trace (and as a result into storage table). We also deploy our service as a package via Azure portal. Introducing of Diagnostics 1.3 is a quite a breaking change for our process, since it requires PowerShell to deploy Diagnostics extension.
I tried to revert back Cloud configuration files (import Diagnostics module) but it is not working. It seems that I have to stay on SDK 2.4 for now.
Is there a way to keep Diagnostics 1.0 but upgrade to Azure SDK 2.5?
Unfortunately No. If you upgrade your Cloud Services to SDK 2.5, you can't use diagnostics 1.0. You have to use 1.3 version of the diagnostics.
We did the same with our projects and faced more or less the same issues as you faced and had to revert back. What we did was kept SDK 2.5 installed on the machines however our projects still use SDK 2.4 i.e. all referenced libraries in our project are from SDK 2.4.
I'm deploying a few Azure services to the Cloud and they fail with the following error, "Unable to reach watchdog.servicebus.appfabriclabs.com" when tryng to connect to the ServiceBus.
When I ping this host the address cannot be resolved. However, when I ping watchdog.servicebus.windows.net this is resolved.
Is there an explicit way to make my services use watchdog.servicebus.windows.net instead? Something wrong with my subscription maybe?
This is likely due to using the CTP/Labs version of the Microsoft.ServiceBus.dll. For Azure production environment you should be using version 1.0, 1.5 or 1.6 corresponding to Azure SDK versions. It appears that you have a version that is targets the LABS environment and may be versioned 2.0/99 etc.
You can obtain the latest ServiceBus client dll from NuGet or downloading the Azure SDK. Another thing to check for is if you have any servicebus.config file in .NET config directories that may be pointing to the LABS environment, more details on that are here.