Hello, I have enabled caching on one of my front door routing rules. Now I need to purge the cache while I deploy the application via Azure DevOps to the respective resource. I've found this option: - job: purge pool: vmImage: ubuntu-16.04 steps: - task: AzureCLI@2 inputs: azureSubscription: ${{ parameters.azure_service_connection }} scriptType: 'bash' scriptLocation: 'inlineScript' inlineScript: | az extension add --name front-door az network front-door purge-endpoint --resource-group ${{ parameters.resource_group}} --name ${{ parameters.front_door}} --content-paths "/" Now I have two questions: What is the difference between az network front-door purge-endpoint and az afd endpoint purge ? az network front-door purge-endpoint requires a name . What's the name here explicitly? Is it the name of the routing rule? In this case "staging-multilanguage"?

Hello @Torben , Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well. I understand you have a couple of questions regarding Azure Front Door purge. I've answered them below: What is the difference between az network front-door purge-endpoint and az afd endpoint purge? az network front-door commands are used to manage Classic Azure Front Doors . https://learn.microsoft.com/en-us/cli/azure/network/front-door?view=azure-cli-latest az afd commands are used to manage Azure Front Door Standard/Premium . https://learn.microsoft.com/en-us/cli/azure/afd?view=azure-cli-latest az network front-door purge-endpoint requires a name. What's the name here explicitly? Is it the name of the routing rule? In this case "staging-multilanguage"? The name parameter in the az network front-door purge-endpoint command is the name of the Azure Front Door. Refer: https://learn.microsoft.com/en-us/cli/azure/network/front-door?view=azure-cli-latest#az-network-front-door-purge-endpoint https://learn.microsoft.com/en-us/azure/frontdoor/standard-premium/how-to-cache-purge-cli So, if you have a Classic Azure Front Door, you can use az network front-door command. If you have a Standard/Premium Azure Front Door, you can use az afd command. Kindly let us know if the above helps or you need further assistance on this issue. Please " Accept the answer " if the information helped you. This will help us and others in the community as well.

Front Door Cache clearing in DevOps Pipeline - which command to use?

Accepted answer

GitaraniSharma-MSFT 47,416 Reputation points Microsoft Employee

2023-03-21T11:06:32.9333333+00:00

Hello @Torben ,

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

I understand you have a couple of questions regarding Azure Front Door purge. I've answered them below:

What is the difference between az network front-door purge-endpoint and az afd endpoint purge?

az network front-door commands are used to manage Classic Azure Front Doors.

https://learn.microsoft.com/en-us/cli/azure/network/front-door?view=azure-cli-latest

az afd commands are used to manage Azure Front Door Standard/Premium.

https://learn.microsoft.com/en-us/cli/azure/afd?view=azure-cli-latest

az network front-door purge-endpoint requires a name. What's the name here explicitly? Is it the name of the routing rule? In this case "staging-multilanguage"?

The name parameter in the az network front-door purge-endpoint command is the name of the Azure Front Door.

Refer: https://learn.microsoft.com/en-us/cli/azure/network/front-door?view=azure-cli-latest#az-network-front-door-purge-endpoint

https://learn.microsoft.com/en-us/azure/frontdoor/standard-premium/how-to-cache-purge-cli

So, if you have a Classic Azure Front Door, you can use az network front-door command.

If you have a Standard/Premium Azure Front Door, you can use az afd command.

Kindly let us know if the above helps or you need further assistance on this issue.

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
Please sign in to rate this answer.
Torben 20 Reputation points

2023-03-21T12:17:55.6666667+00:00

Hey @GitaraniSharma-MSFT ,

thanks for your quick response. You said, that the "name" as a parameter is the name of the Front Door. But what exactly is the name of the Front Door?

In my Front Door View, I have several entries in Frontends, Backend-Pools and Routing Rules. I only want to purge the cache for Routing Rule "staging-multilanguage". But what name do I need to use here?

GitaraniSharma-MSFT 47,416 Reputation points Microsoft Employee

2023-03-21T13:08:12.4166667+00:00

Hello @Torben ,

If you have a Classic Azure Front Door resource, then you can check the Overview page of the Azure Front Door in Azure portal and look for the frontend host. The name before azurefd.net is your Azure Front Door name:

It is the default frontend host, which is a subdomain of azurefd.net and was added as a globally unique name for your Azure Front Door during its creation.

Refer: https://learn.microsoft.com/en-us/azure/frontdoor/quickstart-create-front-door-cli#create-the-front-door

If you have a Standard/Premium Azure Front Door resource, then the name will be available on the Overview page of the Azure Front Door in Azure portal as below:

Now, coming the cache purge part,

Azure Front Door Classic supports:

Single path purge: Purge individual assets by specifying the full path of the asset (without the protocol and domain), with the file extension, for example, /pictures/strasbourg.png;

Wildcard purge: Asterisk () may be used as a wildcard. Purge all folders, subfolders, and files under an endpoint with / in the path or purge all subfolders and files under a specific folder by specifying the folder followed by /, for example, /pictures/.

Root domain purge: Purge the root of the endpoint with "/" in the path.

Refer: https://learn.microsoft.com/en-us/azure/frontdoor/front-door-caching?pivots=front-door-classic#cache-purge

Azure Front Door Standard/Premium supports:

Single path purge: Purge individual assets by specifying the full path of the asset (without the protocol and domain), with the file extension, for example, /pictures/strasbourg.png.

Root domain purge: Purge the root of the endpoint with "/*" in the path.

Refer: https://learn.microsoft.com/en-us/azure/frontdoor/standard-premium/how-to-cache-purge

When you say, "only want to purge the cache for Routing Rule 'staging-multilanguage'", what exactly you are referring to here?

There is no cache purge setting for a routing rule. You can only purge single content paths or root domain.

When using the az network front-door purge-endpoint command to purge AFD cache, you need to provide the content path which you would like to purge.

--content-paths : The path to the content to be purged. Can describe a file path or a wildcard directory.

Refer: https://learn.microsoft.com/en-us/cli/azure/network/front-door?view=azure-cli-latest#az-network-front-door-purge-endpoint

So, if you would like to purge the paths included in the 'staging-multilanguage' routing rule, then you need to add those specific paths when running the cache purge command.

You can see the paths included in a routing rule as below:

NOTE: Cache purges on the Front Door are case-insensitive. Additionally, they're query string agnostic, which means that purging a URL purges all query string variations of it.

Kindly let us know if the above helps or you need further assistance on this issue.

Regards,

Gita

Torben 20 Reputation points

2023-03-23T11:27:24.2766667+00:00

Hello Gita,

thanks for getting back to me.

I understand what's the name now, in our case we have a Classic Front Door Instance and therefore a name with *.azurefd.net

Regarding the purging: I still struggle to understand the behaviour here. So I have several routing rules currently and only on one of these rules I have enabled the cashing/compression functionality. This setting looks like this:

So I need to purge the cache for "/**" ?* What happens if I add cashing to one of the other routing rules that also have a path set to "/*" ?

I need to somehow be able to distinguish between purging the cache on this routing rule and on other routing rules... as I do not want to purge the cache of the production environment when the staging environment deploys...

GitaraniSharma-MSFT 47,416 Reputation points Microsoft Employee

2023-03-24T14:23:22.0833333+00:00

Hello @Torben ,

As mentioned before, purge cannot be done at routing rule level for any Azure Front Door SKU.

However, Azure Front Door Standard/Premium supports selecting/defining one or more endpoints and entering the domain and or subdomains you want to purge from the edge nodes along with the content paths.

Refer: https://learn.microsoft.com/en-us/azure/frontdoor/standard-premium/how-to-cache-purge

But Azure Front Door Classic can accommodate only one endpoint. So, purge command would purge that endpoint. Domain/sub-domain level purge is not supported.

Refer: https://learn.microsoft.com/en-us/azure/frontdoor/manager#front-door-manager-classic

So, if you've enabled caching on 2 routing rules with path set to "/" and perform a cache purge for “/”, both the rules will be affected, as Azure Front Door Classic will do the purge on the endpoint level.

If you wish you may leave your feedback in the below forum requesting a feature which might help. All the feedback you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building Azure.

https://feedback.azure.com/d365community/forum/8ae9bf04-8326-ec11-b6e6-000d3a4f0789

Now, I would like to share some more details that might help here:

If you use Azure Front Door Standard/Premium SKU, then you can add multiple endpoints. An endpoint is a logical grouping of one or more routes that are associated with domain names. Each endpoint is assigned a domain name by Front Door, and you can associate your own custom domains by using routes.

https://learn.microsoft.com/en-us/azure/frontdoor/endpoint?tabs=azurecli

This way, you can differentiate your production and staging environments and perform cache purge only on the staging environment endpoints/domains.

If interested, you may look into the Migration capability for Azure Front Door which is currently in PREVIEW.

Azure recommends migrating to the newer tiers to benefit from the new features and improvements over the Classic tier. To help with the migration process, Azure Front Door provides a zero-downtime migration to migrate your workload from Azure Front Door (class) to either Standard or Premium tier.

Refer: https://learn.microsoft.com/en-us/azure/frontdoor/tier-migration

Kindly let us know if the above helps or you need further assistance on this issue.

Regards,

Gita
Sign in to comment

Front Door Cache clearing in DevOps Pipeline - which command to use?

0 additional answers