You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to change from functionscdn.azureedge.net to cdn.functions.azure.com.
In this repo, that means changes to the feed content itself, across all versions. Please consider changing that as a separate PR, and maybe creating a corresponding sub-item.
This repo will also require changes to the generator tool that CI uses:
We also include a direct reference (to an old version!) in the readme, which we arguably should replace with an aka link of some kind. I can help with creating that.
The Azure Functions Tooling Feed is consumed by Visual Studio and Visual Studio code to make sure they are always using the latest [core tools](https://github.com/Azure/azure-functions-core-tools) and matching [templates](https://github.com/Azure/azure-functions-templates). The Azure Functions Tooling Feed is hosted at https://functionscdn.azureedge.net/public/cli-feed-v3.json.
Changes will also be needed to the release pipelines in ADO.
The text was updated successfully, but these errors were encountered:
We need to change from
functionscdn.azureedge.net
tocdn.functions.azure.com
.In this repo, that means changes to the feed content itself, across all versions. Please consider changing that as a separate PR, and maybe creating a corresponding sub-item.
This repo will also require changes to the generator tool that CI uses:
azure-functions-tooling-feed/GenerateToolingFeed/V3Format/V3FormatFeedEntryUpdater.cs
Line 68 in a026919
azure-functions-tooling-feed/GenerateToolingFeed/V4Format/V4FormatFeedEntryUpdater.cs
Line 112 in a026919
We also include a direct reference (to an old version!) in the readme, which we arguably should replace with an aka link of some kind. I can help with creating that.
azure-functions-tooling-feed/README.md
Line 3 in 40e88c9
Changes will also be needed to the release pipelines in ADO.
The text was updated successfully, but these errors were encountered: