From 24115af0940f8d6b435674d1b37b4395c169891f Mon Sep 17 00:00:00 2001 From: Ari Kalfus Date: Thu, 9 Feb 2023 20:45:49 -0500 Subject: [PATCH] Update README.md --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 48855f0..27be1ac 100644 --- a/README.md +++ b/README.md @@ -782,6 +782,7 @@ However, for the sake of this course, we've configured Vault roles in the same w - We'd love to hear what you thought of this course [in our discussion board](https://github.com/artis3n/course-vault-github-oidc/discussions). - You can combine multiple claims in a single Vault role to provide even more fine-grained access control! For example, learn how to combine `sub` and `job_workflow_ref` to [provide secrets for reusable workflows](https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows). +- Read [this comprehensive article](https://www.digitalocean.com/blog/fine-grained-rbac-for-github-action-workflows-hashicorp-vault) to learn how DigitalOcean employs this GitHub OIDC pattern for streamlined secrets management. - Use this [Terraform module](https://github.com/digitalocean/terraform-vault-github-oidc) from DigitalOcean to help manage your GitHub OIDC Vault role configurations.