I am curious if some of you have found a good way to provide a standard set of ci/cd templates via github actions without it ending in tears

Hello Leon! I found these videos good balance between high level with some insights on certain Platform engineering areas. In my opinion, they set a good outlook on why Platform matter and explains why product mindset is important while building one.

@Tomek Fiechowski I'm just trying to figure it all out at the moment as to what this means in a medium / large corporation

not to just plug our own product @Pieter but I'm curious if something like https://www.withcoherence.com/ would help you with sharing best practices across projects without copy/pasting tons of templates

Hey @Pieter! I can speak from a small org size (±20 devs) what we found with GitHub Actions was being able to provide workflow templates that give teams a "golden path" for their apps/services. We're still in the process of moving to an actual IDP, but we try to encourage them not to stray too far from the standard way we do things for the meantime. Specifically, we have a repo with all our (versioned) action workflows in a

.github/workflows/

directory that trigger on

workflow_call

and have

inputs

and

secrets

that can be passed in. This allows teams to create their own workflows in other repos that simply "call" the shared workflow with inputs and secrets. e.g.

uses: org-name/repo-name/.github/workflows/build-deploy-v1.yml@master
with:
  input-name: "value"
secrets:
  secret-name: "value"

Works pretty well for us at this scale 🙂 happy to share details! (Might even write up post on our blog soon for the general public...)