AzureStorageExplorer
AzureStorageExplorer copied to clipboard
microsoft
If Front Door/CDN is configured for blob, then CopyURL should use that endpoint instead of default.
Preflight Checklist
- [X] I have installed the latest version of Storage Explorer.
- [X] I have checked existing resources, including the troubleshooting guide and the release notes.
- [X] I have searched for similar issues.
Problem
I want to get the CDN path to the blob, not the default storage account endpoint.
Desired Solution
Right click on file and get the CDN path.
Alternatives and Workarounds
No response
Additional Context
No response
@jongio we don't have a ton of experience with CDN/front door. Can you guide us to some docs that might give us an idea as to the feasibility of this? My brain has some initial open questions like:
- How do we know if a container is hooked up to a CDN?
- How do we get/construct the CDN equivalent blob url?
PS: Nice to see a feature request from you again! Been a while. 😁
Related to: https://github.com/microsoft/AzureStorageExplorer/issues/334
You configure the storage account as an 'origin group' when you setup the CDN, but I'm not seeing that info in ARM. They must have a data plane for that data. Do you know anyone on CDN team that could help?
At a min, maybe we let the user manually configure an alternate root endpoint and then append the path to that instead of the blob path.
{my custom path to cdn}/{the relative path to the file}
Hmm this is all reminiscent of what I remember when I've looked into CDN integration before. All of the "linkage" between CDN and Storage is CDN → Storage. Or in other words, from a storage account/container based point of view, there is no (easy) way to know that CDN is using the account/container as an origin group/origin/etc.
The only way to do it automatically would be to look through every CDN you have, get its origin groups/origins, and see if one of those is for the current account/container. For someone with a small amount of CDNs/CDN origin groups/origins, this probably isn't terrible, but for someone with a lot, I can see it taking a while.
Do you know anyone on CDN team that could help?
No I do not. If you can find one let me know. :)
They must have a data plane for that data.
I don't see any data plane APIs for CDN, just ARM.
At a min, maybe we let the user manually configure an alternate root endpoint and then append the path to that instead of the blob path.
Eh I'm dubious about this. I think ultimately what most customers interested in this would want is to have Storage Explorer "just work", and have the "Copy CDN URL" option as originally described. Making folks manually enter in yet another endpoint does not sound like a good way to make people happy.
As of today, is it not easy enough to just do "Copy Path" (which copies the relative path) and then add that on to the CDN URL?
As of today, is it not easy enough to just do "Copy Path" (which copies the relative path) and then add that on to the CDN URL?
Possible yes, and that is what I do today, but without coding I have to do it manually.
Until we can get a better capability from the CDN/storage APIs to be able to quickly link storage accounts/containers to a CDN, we're going to put this in future for now. If folks are interested in this, please 👍 react the original issue comment. Thanks!