Finally found a solution to clear the CDN cache using GitHub Actions!

Stefano — Wed, 24 Jul 2024 13:21:18 +0000

Why?

I've been struggling for a while to find a way to clear the CDN cache using GitHub Actions. I tried a few different methods, but none of them worked quite right. Finally, I found the solution!

The solution is to use the Invalid CDN cache on GCP action from the GitHub Marketplace. This action makes it easy to add CDN cache invalidation to your pipeline.

Setup

Before using this action, you must first use the google-github-actions/auth action to authenticate to Google Cloud.

Required inputs:

load-balancer-name: The name of the load balancer. This value can be found in the Google Cloud Console.
path: The path to the content that you want to invalidate. This value must be a valid URL path. For example:
- to invalidate the cache for the /index.html file, you would set the path input to /index.html.
- to invalidate the whole directory, you would set the path input to /images/*.
- to invalidate everything, you would set the path input to /*.

Optional inputs:

host: The hostname of the CDN endpoint. If you do not specify a hostname, the action will use the default hostname for the load balancer.
gcloud_version: Version of the Cloud SDK to install. If unspecified or set to "latest", the latest available gcloud SDK version for the target platform will be installed. Example: "290.0.1".
gcloud_component: Version of the Cloud SDK components to install and use.

Example usage:

name: Invalidate Google Cloud CDN Cache

on:
  push:
    branches: [ main ]

jobs:
  invalidate-cache:
    runs-on: ubuntu-latest

    steps:
     - name: Authenticate to Google Cloud
       uses: google-github-actions/auth@v2
       with:

     - name: Invalid CDN cache on GCP
       uses: stefanodotit/github-actions-invalidate-gcp-cdn@v1
       with:
          load_balancer_name: LOAD_BALANCER_NAME
          path: '/path/to/invalid/*'

I highly recommend this action to anyone who needs to clear their CDN cache using GitHub Actions.

Additional notes:

You can find more information about the action on the GitHub Marketplace: https://github.com/marketplace/actions/invalid-cdn-cache-on-gcp
You can also find more information about GCP's CDN API on the Google Cloud documentation website: https://cloud.google.com/cdn

I hope this helps!

P.S. If you have any other questions, please feel free to leave a comment below.

How to change a file locally without commit it on Git

Stefano — Mon, 04 Apr 2022 14:12:16 +0000

Scenario

I wanted to freeze a file in git, so that when someone commits, this file is not updated.
The scenario was something like that: I need an ENV variable that usually will be available only on CI/CD to take the right token but on the local side I don't need it.

The Problem

So I want a file that will be on my repository, and will be versioned but I want to change it on the local side and not commit it (I can skip it every time without include it on git add but it's so boring and in long term will not work).
I tried a different hack solution like .gitignore but it did not work.
So I read some documentation and I discovered the update-index option on git.

How update-index works

With this command:
git update-index --assume-unchanged <file>
Are you basically changing the assume unchanged bit and are you forcing Git to pretend it never changes.
In this way Git will exclude this file from any tracking, so you can modify it on the local side and basically forget it.

If you want to came back to the "normal version" u can easily exec this command:
git update-index --no-assume-unchanged <file>
and everything will come back like before.

If u want to check what kind of files are with this active flag you can easily run:
git ls-files -v
Files where the flag is --assume-changed have H, --assume-unchanged is h.

DEV Community: Stefano