Closed robertleelarson closed 2 years ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @cdnfdsuppgithub.
CDN team, please help to look into this question.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @cdnfdsuppgithub.
It's been 6 months. Figured I'd follow back up with down time past launch. I'd like to get this all working again. I have not tried any new releases of any clis, sdks, etc.. with the original script at this time.
Hello @robertleelarson Apologies for the delayed response. I see that this issue is opened a long time ago and no further activity had taken place. So wanted to check if you are still looking for assistance on this query? Please let us know.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @cdnfdsuppgithub.
Author: | robertleelarson |
---|---|
Assignees: | - |
Labels: | `Network - CDN`, `Service Attention`, `question`, `customer-reported`, `needs-author-feedback`, `needs-team-triage` |
Milestone: | - |
I was forced to move on with minimal time available to come back. To be fair, as a customer i can't keep taking time to follow up with all the updates to see if it's going to work. I'd ask Microsoft to take a look and verify if they've resolved it and post back the results whether it's resolved in a future update that was made available.
@robertleelarson Apologies for the delayed response. We are looking into this issue and will get back once we have an update.
@t-bzhan Please update this github thread once you get a chance.
Hi @robertleelarson, Az.Cdn module added support for multiple origin since 1.6.0. The per-origin level origin host header update is supported as part of the implementation.
I tested with my local installed Az.Cdn 1.8.1, that works as expected.
PS C:\WINDOWS\system32> $origin = Get-AzCdnOrigin -OriginName $originName -EndpointName $environmentEndpointName -ProfileName $sharedCDNProfile -ResourceGroupName $sharedResourceGroupName PS C:\WINDOWS\system32> $origin
HostName : huaiyiztesthost1.blob.core.chinacloudapi.cn
HttpPort : 80
HttpsPort : 443
OriginHostHeader : huaiyiztesthost2.blob.core.chinacloudapi.cn
Priority : 1
PrivateLinkApprovalMessage :
PrivateLinkLocation :
PrivateLinkResourceId :
Weight : 1000
ResourceState : Active
ResourceGroupName : bzhan-poc
ProfileName : msft-test
EndpointName : cachekeytest
Id : /subscriptions/27cafca8-b9a4-4264-b399-45d0c9cca1ab/resourcegroups/bzhan-poc/providers/Mic
rosoft.Cdn/profiles/msft-test/endpoints/cachekeytest/origins/huaiyiztesthost1-blob-core-ch
inacloudapi-cn
Name : huaiyiztesthost1-blob-core-chinacloudapi-cn
Type : Microsoft.Cdn/profiles/endpoints/origins
ProvisioningState : Succeeded
PS C:\WINDOWS\system32> $origin.OriginHostHeader="huaiyiztesthost1.blob.core.chinacloudapi.cn"
PS C:\WINDOWS\system32> $origin | Set-AzCdnOrigin
HostName : huaiyiztesthost1.blob.core.chinacloudapi.cn
HttpPort : 80
HttpsPort : 443
OriginHostHeader : huaiyiztesthost1.blob.core.chinacloudapi.cn
Priority : 1
PrivateLinkApprovalMessage :
PrivateLinkLocation :
PrivateLinkResourceId :
Weight : 1000
ResourceState : Active
ResourceGroupName : bzhan-poc
ProfileName : msft-test
EndpointName : cachekeytest
Id : /subscriptions/27cafca8-b9a4-4264-b399-45d0c9cca1ab/resourcegroups/bzhan-poc/providers/Mic
rosoft.Cdn/profiles/msft-test/endpoints/cachekeytest/origins/huaiyiztesthost1-blob-core-ch
inacloudapi-cn
Name : huaiyiztesthost1-blob-core-chinacloudapi-cn
Type : Microsoft.Cdn/profiles/endpoints/origins
ProvisioningState : Succeeded
Please update the Az.Cdn module version to see whether the issue is addressed.
I have set up a Microsoft Azure CDN. That CDN has a custom domain and certificate issued from within Azure. It points to the one Domain I need a single $web based Blob storage container with my angular files. The goal was to spin up containers per release with the iteration of Angular files required, then update the CDN to point back to that blob storage container. This would facilitate a quicker rollback by knowing I kept the previous state of the environment intact for a few moments.
The issue is OriginHostHeader that is required by Blob storage web hosted objects is not updateable on an origin object. Given the new Origin Groups setting in the CDN as well, it is thoroughly complaining that with the potential of multiple defined origins (even though I have one who is set to default) that it must be defined at the Origin Level and not the Endpoint.
There is only place I have found where you can modify the OriginHostHeader and that is at the EndPoint level. The concern there is it is still using the First storage account's URL. With the Origin Groups in place, it will not take an edit anymore at the endpoint level.
This pattern I had of updating via the Endpoint used to work until the Origin Groups showed up in the portal.
Before anyone suggests to pull latest, latest is not supported in Azure DevOps and the all documentation for ARM, Az, and API do not have a field for OriginHostHeader that can be updated at the Origin level, even though there is one in the GUI.
Steps to reproduce
Create a Microsoft CDN. Create an initial origin by hand and point it to an existing container. Create a new container to host a second version of your site.
Grab the Origin
There is no field for OriginHostHeader
This works, but there is zero field to update. Move the update to the Endpoint.
This used to work before having to specify a default Origin in an endpoint via the Groups
but is now complaining that multiple may exist and should be iterated at the Origin level
Environment data
Name Value
PSVersion 7.0.3 PSEdition Core GitCommitId 7.0.3 OS Microsoft Windows 10.0.18363 Platform Win32NT PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…} PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1 WSManStackVersion 3.0
Module versions
Debug output
Error output