Update CDN endpoint #8595
Update CDN endpoint #8595
Conversation
|
Wait to January to merge as it'll get picked up in the pipeline right away and we don't want to risk it |
|
Which .NET SDK branches will this change get applied to? |
|
This only applies to the main branch. The only hardcoded urls are part of a backend content generation process, the results of which are downloaded by user SDK installations through another redirect that isn't subject to the work we have to do for this one. This process only happens out of main (and maintaining the compatibility of the results is a constraint that we have to operate under). |
|
I see. I hear you saying that the scope here is very narrow. That's good. |
|
We will want to consider moving to a vanity domain instead of AFD directly. We can discuss that offline. If it's worth using a CDN, it is likely worth using a vanity domain. |
|
Went ahead and merged this because we want to use templating as a low-blast-radius test of the AFD infrastructure to inform some decision making happening on Monday. @marcpopMSFT I added you to the internal thread discussing this for the full context. |
No description provided.