You're reading from Mastering GitHub Actions

Product type Book

Published in Mar 2024

Publisher Packt

ISBN-13 9781805128625

Pages 490 pages

Edition 1st Edition

Languages

Concepts

DevOps

Author (1):

Eric Chapman

Table of Contents (22) Chapters

Preface

1. Part 1:Centralized Workflows to Assist with Governance

2. Chapter 1: An Overview of GitHub and GitHub Actions

3. Chapter 2: Exploring Workflows

4. Chapter 3: Deep Dive into Reusable Workflows and Composite Actions

5. Chapter 4: Workflow Personalization Using GitHub Apps

6. Chapter 5: Utilizing Starter Workflows in Your Team

7. Part 2: Implementing Advanced Patterns within Actions

8. Chapter 6: Using HashiCorp Vault in GitHub

9. Chapter 7: Deploying to Azure Using OpenID Connect

10. Chapter 8: Working with Checks

11. Chapter 9: Annotating Code with Actions

12. Chapter 10: Advancing with Event-Driven Workflows

13. Chapter 11: Setting Up Self-Hosted Runners

14. Part 3: Best Practices, Patterns, Tricks, and Tips Toolkit

15. Chapter 12: The Crawler Pattern

16. Chapter 13: The Configuration Centralization Pattern

17. Chapter 14: Using Remote Workflows to Kickstart Your Products

18. Chapter 15: Housekeeping Tips for Your Organization

19. Chapter 16: Handy Workflows for Managing Your Software

20. Index

Why subscribe?

21. Other Books You May Enjoy

Setting up a workflow to use HashiCorp

This section aims to introduce a new workflow and a vault action. This workflow will allow us to notify Slack of the build outcome. We want this to be a reusable workflow within our organization so that any build outcome will go to a channel for the team.

We’ll add the build-node action we created in previous chapters and a new reusable workflow to the GHA.Private.Templates repository we created in the previous chapter. You can get the build action from the Chapter 6/.github/actions/* file and the reusable workflow we will use from Chapter 6/.github/workflows/gha.workflows.build-node.yml. You will need to update the value of YOUR_VAULT_URL_HERE in this file to point to your public cluster URL, which you can get from your cluster overview page.

Copy the actions directory from the repository into the private template repository for the organization. This file won’t be changed, and we’ve used this before, so we won’...