Replace Your GitHub Actions YAML with CUE

Are you tired of copy-pasting YAML between repositories only to be bitten by typos after pushing?

In this tutorial, we explore how to replace brittle GitHub Actions YAML with CUE - a powerful configuration language that brings type safety, validation, and reusability to your pipelines.

We walk through the process of adopting CUE incrementally, allowing you to keep the parts of GitHub Actions you love while removing the pain of managing massive YAML files. You'll learn how to treat your configuration as code, enforce policies, and generate your final YAML artifacts automatically.

In this video, we cover:

• CUE Basics: Understanding how CUE combines schema and data to validate inputs (for example, our example will show how to ensure age constraints).
• Validation: Using cue vet to catch mistakes and validate workflows against schemas before you push.
• The CUE Central Registry: Importing existing GitHub Actions definitions to get instant validation for your pipelines.
• Importing & Exporting: How to convert existing YAML files into CUE (cue import) and generate valid YAML back out (cue export).
• DRY Workflows: Creating reusable triggers and modules to avoid code duplication across your repositories.
• Security: How to use CUE to pin action versions to specific SHAs for safer, compliant builds.

Resources:

• CUE Central Registry Documentation: https://cue.dev/docs
• CUE Central Registry: https://registry.cue.works/
• More about the CUE project: https://cuelang.org

Resources related to this video will be displayed here, including links, downloads, and additional materials.