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

Clarification on Migration of functionscdn.azureedge.net Subdomain #2576

Open
cetinbug opened this issue Jan 10, 2025 · 1 comment
Open

Clarification on Migration of functionscdn.azureedge.net Subdomain #2576

cetinbug opened this issue Jan 10, 2025 · 1 comment

Comments

@cetinbug
Copy link

cetinbug commented Jan 10, 2025

We are using Azure Functions and rely on the CDN functionscdn.azureedge.net to retrieve extension bundles. However, after reviewing the information provided in the GitHub issue: "Critical: .NET install domains and URLs are changing", I noticed that there is no specific mention of the functionscdn subdomain in the migration details.

Could you please clarify:

Whether the functionscdn.azureedge.net subdomain is also part of the migration process?
If yes, to which domain will it be migrated?
For reference, we currently retrieve extension bundles using a URL similar to:

https://functionscdn.azureedge.net/public/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle.Preview/$EXTENSION_BUNDLE_VERSION This clarification will help us ensure uninterrupted operations and allow us to prepare for any required changes.

@mattchenderson
Copy link

Hi - we're tracking this and are working on the migration plan for this subdomain. We do not presently have a new domain identified. Once we do, we will provide an update here with guidance.

In the meantime, our primary recommendation is to prepare for a migration by making the domain configurable in whatever components depend on it. We intend for the new domain to be path-compatible with the existing one.

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

No branches or pull requests

2 participants