Status Updates From GitHub Actions in Action: C...

OIDC workflows finally provide breath (AWS, Azure, GCP). But, they only show auth and then echo their env to show they were allowed. It would have been more useful to show more fleshed out workflows that actually do something useful with the credentials. Red-green deployment was all over the place.

Looking at continuous deployment support, including deployment environments and secrets, like credentials.

Chapter on CI sets up more useful and realistic workflows. But their treatment is still very superficial and does not explain adequately the underlying mechanisms. The examples use .NET, but additional examples for Java and Node (and Ruby) would have been helpful. The examples generate Docker images, but what if I have other types of deployment artifacts?!?

We're getting into a more "real life" example. Too bad it's in .NET. Who thought it would be a good idea to have a hardcoded test summary instead of building one from some test resuls?

Authoring actions as repos with "action.yml" files, one in top-level directory, or monorepo-style with each action in its own directory. JavaScript actions execute the fastest, but Docker image ones can be in any language.

Examples are easy to follow. There is an uneasy balance of showing possibilities vs. referring the reader to the online documentation. While they keep recommending the online workflow editor, they do mention VS Code, and I'm using WebStorm.