Our great sponsors
-
-
ci
A GitHub Action and Azure DevOps Task designed to simplify using Dev Containers (https://containers.dev) in CI/CD systems. (by devcontainers)
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
This is one of the reasons ive done a poc on github. Unfortunately still YAML, but its the only actively maintained way with huge amount of support from community so more likely to find something if you need a specific usage case.The other venue im looking into is using dagger.io to basically not be locked to a specific CICD provider. I might not enjoy all the latest and greatest the specific platofrm is giving me but I can maintain the same workflow no matter the platofrm.
Use a vscode devcontainer for your local development. This devcontainer has all of your tooling inside it. You maintain it, you control what versions of libraries and tools it has. This devcontainer should also be able to deploy the app/infrastructure so your developers can work in their sandbox. Then.....in your yaml (ghactions/azdo) all you do is build your devcontainer and run the commands inside your container. https://code.visualstudio.com/docs/devcontainers/devcontainer-cli. This way, your yaml is simple and your complicated build/deploy logic is kept alongside the code. What works on your local machine, truly works in your build.... Here are the build tasks https://github.com/devcontainers/ci