Hello! 👋

This is my resume hosted in Azure. This is part of the A Cloud Guru Challenge.

⭐My Resume⭐ Blog Post

Challenges:

• Create a GitHub repo.
• Use HTML and CSS to build the website and store the code in the repo.
• Add a visitor count to the website.
• Deploy the website to Azure Blob Storage.
• Enable HTTPS and custom domain support.
• Set up GitHub Actions.
• Write a blog post.

I had already kind of did the AWS challenge which ACloud Guru posted in 2020 (I kind of did it back in 2019), the Cloud Resume Challenge. Back then, I was just starting to learn AWS, and I wanted to have a project to show my cloud skills, as I was learning all these new services. It's fun to do it in Azure 😄

• Tutorial: Host a static website on Blob Storage

• Quickstart: Create an Azure CDN profile and endpoint
• Tutorial: Map a custom domain with HTTPS enabled

• Tutorial: Use GitHub Actions to deploy your static website to Azure storage
• This workflow is compromised of 4 tasks:
  • Checkout: this will checkout our code, so the workflow can access it.
  • Azure Login: this will perform a login to Azure, so we can run commands. This is the az login command.
  • Azure CLI: this allows us to automate our workflow by executing Azure CLI commands. We'll use this task twice; first to upload our content to the blob storage and after that to purge the CDN endpoint.
• I encountered an issue with the Purge CDN endpoint task.
• This is the command to run to purge the CDN endpoint: az cdn endpoint purge --content-paths "/*" --profile-name "CDN_PROFILE_NAME" --name "CDN_ENDPOINT" --resource-group "RESOURCE_GROUP"
• The --profile name argument is the actual name of the CDN profile resource.
• The --name argument is the name of the endpoint, as it appears in the hostname mywebsite.azureedge.net.
• When you add an endpoint to your CDN profile, a new resource is created with a long name. This is not the name we should use for our command.