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.

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

Documentation outdated for version 5 #2972

Open
GeorgeNarcis opened this issue Apr 6, 2023 · 4 comments
Open

Documentation outdated for version 5 #2972

GeorgeNarcis opened this issue Apr 6, 2023 · 4 comments

Comments

@GeorgeNarcis
Copy link

We are currently using version 4.0.1 and want to update to the new major version 5.
We are currently using for setup the method AddAzureStorageCoreServices as stated in the docs here: https://learn.microsoft.com/en-us/azure/app-service/webjobs-sdk-get-started.

However after updating to v5 we get an error this method no longer exists and we don t know if we need to install another package for it or it was renamed/removed.

Expected behavior

Documentation should be updated to say how this method was replaced in version 5,

Actual behavior

We get an error after updating and i can t find any documentation on what changed or how can i update.

@ghost ghost assigned fabiocav Apr 6, 2023
@timmkrause
Copy link

Same here.

@Andreas-Lehmann
Copy link

The Solution is to add the latest version of the Microsoft.Azure.WebJobs.Host.Storage NuGet package (5.0.0 for now). This will bring back the .AddAzureStorageCoreServices() extension.
Hope this helps anyone with the same problem or to update the docs.

@shyamal890
Copy link

What is the purpose of .AddAzureStorageCoreServices I am asking because now we have separate components for Queues and Blobs with Microsoft.Azure.WebJobs.Extensions.Storage

So not sure if .AddAzureStorageCoreServices is even needed now. But would appreciate some confirmation here.

@fonbrauzen
Copy link

fonbrauzen commented Nov 20, 2023

@shyamal890 I'm not part of this product dev team, but here is my AFAIK (when I asked myself the same question).
When your job is running it's:

  1. creating short logs "started", "finished" on each run (visible if click on the logs button to the right of the job)
  2. automatically running constantly the monitoring job

Eventually, you'll have a couple of JSONs stored in this storage account.
If you don't have this storage account - some of the buttons in the UI of the Azure app service will lead to errors, due to the absence of these JSONs (as far as I remember at least 1 above).
So think about this as a part of jobs infrastructure in Azure, but for sure they could work without this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants