terraform-up-and-running-code VS actions-workflow-samples

Terraform: Up & Running. O'Reilly Media, Brikman, Y.

There’s a new edition of Terraform: Up & Running that was published last year.

Terraform: Up and Running - Excellent read on using Terraform

If you’re looking for general terraform this is your best bet https://www.terraformupandrunning.com

You should also check this out : https://github.com/brikis98/terraform-up-and-running-code/tree/3rd-edition. Its the companion repo to an actual book which i recommend as well but this series of blog posts by the author maps to the first five chapters of the book so you can explore and see if you want to splurge for the book.

OP, do this, I'm going through the 3rd edition right now to evaluate it as a teaching tool for my colleagues and all examples are up to date and his explanation style is fantastic. You can see he even made some recent updates to the repo 3 days ago: https://github.com/brikis98/terraform-up-and-running-code

GitHub Actions for Azure (official examples): https://github.com/Azure/actions-workflow-samples

appcontent.yml - Used to deploy my app content to the Azure App Service. Using this sample provided by Microsoft, with very minor modifications.

It's using GitHub Secrets. This guide helps: https://github.com/Azure/actions-workflow-samples/blob/master/assets/create-secrets-for-GitHub-workflows.md

For this exercise we need a personal access token from github. To ensure that the action has access to the GitHub token which you, by the way, should never expose to the public - we will place it in the secrets of the repo.

First we'll need to make some repo secrets. Here's a nice guide from Azure explaining how to do just that. It isn't difficult at all.

Add Actions secrets for the FTPS credentials. In our example the secret names are WP_USER and WP_PASSWORD.

Yep. For the projects I’ve worked on, the Azure Functions for scheduling were in their own `functions` folder at the root of the repository. Upon successful deployment of the main app, we’d then deploy the functions. Aside from that deployment happening after the main app’s, we use the same deployment configuration as the official example for GitHub Actions with Python functions: https://github.com/Azure/actions-workflow-samples/blob/master/FunctionApp/linux-python-functionapp-on-azure.yml.

We have 1 user that we use for deployment. We keep the username and password of this user in a Secret (all platforms support some form of secrets, here is some docs on Github Actions specifically).

I followed the official documentation (Link) and used the pre-defined template and it worked out of the box.