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 migrate dotnetbuilds over to AzureFD due to the Edgio CDN going away. Unlike dotnetcli, we can change the hostname in the places it is referenced (dotnetbuilds.azureedge.net). dotnetbuilds is not intended for general public consumption of .NET bits, though it is referenced in our official install scripts.
Execution Steps
The plan for migration off of dotnetbuilds is as follows:
Create a new CDN that points to the dotnetbuilds storage account. This CDN will have the same settings as the previous CDN. Note that azurefd FQDNs include a hash and are less friendly to work with.
Determine and create a short form URL that should point to the new dotnetbuilds CDN. This short form could be a subdomain of dot.net, or an aka.ms link, etc.
.NET Dockerfiles reference dotnetbuilds for nightly builds and some other releases. Today only the Aspire Dashboard Dockerfile references it. We would add more references when we add .NET 10 nightly Dockerfiles, but obviously we will just point that at wherever the new build location is. We can update these at any time, but historical nightly Dockerfiles will fail to build.
We need to migrate dotnetbuilds over to AzureFD due to the Edgio CDN going away. Unlike dotnetcli, we can change the hostname in the places it is referenced (dotnetbuilds.azureedge.net). dotnetbuilds is not intended for general public consumption of .NET bits, though it is referenced in our official install scripts.
Execution Steps
The plan for migration off of dotnetbuilds is as follows:
When the old URI dies, the announcement should be updated to indicate that this is the case.
The text was updated successfully, but these errors were encountered: