Merge pull request #6 from githubpartners/build-deploy-azure

Build and deploy applications to Azure by using GitHub Actions

Author: rmallorybpc

github/github-actions-cd/includes/2-deploy-azure.md

@@ -16,6 +16,8 @@ on:
     types: [labeled]
 ```
 
+Workflow re-runs in GitHub Actions will use the initial run’s actor for privilege evaluation. The actor who triggered the re-run will continue to be displayed in the UI, and accessed in a workflow via the `triggering_actor` field in the `github` context.
+
 ## Control execution with a job conditional
 
 Often, you only want to run a workflow if some condition is true. 
@@ -163,4 +165,8 @@ steps:
 
 ```
 
-Notice that you use GitHub actions to check out the repository and to sign in to Azure. After that, you create the resources you need and deploy the container by using the Azure CLI.
+Notice that you use GitHub actions to check out the repository and to sign in to Azure. After that, you create the resources you need and deploy the container by using the Azure CLI.
+
+## Disable Actions workflows
+
+You can temporarily disable a GitHub Actions workflow either in the UI or through the API. This functionality allows you to stop a workflow from being triggered without having to delete the file from the repo. Later, you can easily re-enable it again from the UI or through the API.

github/github-actions-cd/includes/2b-manage-workflow-runs.md

@@ -71,4 +71,8 @@ So, for example, let's say you need to create a workflow to a production environ
 2. Configure the required reviewers environment protection to require an approval from the specific dev team.
 3. Configure the specific job within the workflow to look for the production environment.
 
+GitHub Actions lets you control the permissions granted to the `GITHUB_TOKEN` secret. The `GITHUB_TOKEN` is an automatically generated secret letting you make authenticated calls to the GitHub API in your workflow runs. Actions generates a new token for each job and expires the token when a job completes. These new settings allow you to follow a principle of least privilege in your workflows. The token has `write` permissions to a number of API endpoints except in the case of pull requests from forks which are always `read`.
+
 You can create and configure new repository environments from the repository's **Settings** tab under **Environments**.
+
+GitHub Actions simplifies using secrets with reusable workflows with the secrets: `inherit keyword`. You can simply pass the `secrets: inherit` to the reusable workflow and the secrets will be inherited from the calling workflow.

github/github-actions-cd/index.yml

@@ -3,7 +3,7 @@ uid: learn.github.github-actions-cd
 metadata:
   title: "Build and deploy applications to Azure by using GitHub Actions"
   description: Create two deployment workflows using GitHub Actions and Microsoft Azure.
-  ms.date: 07/08/2022
+  ms.date: 08/08/2022
   author: a-a-ron
   ms.author: aastewar
   ms.topic: interactive-tutorial