TL;DR
CloudSkiff now supports the full GitOps workflow, with branches and pull requests.

Committing directly to master and then applying was OK when you were alone and not doing anything critical. But where did the engineering best practices go? Where are the code reviews? Where are the automated checks?

With this release, CloudSkiff supports a clean, collaborative workflow, that comes together with our simple role-based permissions :

1. Create a branch with your fix.
2. Create a pull request - it will be visible on CloudSkiff.
3. CloudSkiff runs automated checks (a linter on the screenshot).
4. A reviewer approves and merges with master.
5. CloudSkiff applies changes and notifies the team.

With this workflow :

• applys are ran automatically from CloudSkiff, so master cannot get out of sync with what is actually running,
• the team has visibility on all the applys (and PRs, and merge) from CloudSkiff,
• team members cannot commit directly to master,
• code reviews and roles are easy to setup,
• CloudSkiff runs automated checks.

As we go, we are improving this workflow even more and adding :

• more checks,
• more automation.

If that resonates with you and you want to share feedback, shoot us an email or tweet @CloudSkiff

And remember, if you know folks excited about Infra as Code, Terraform, and automation

⬇️ invite them to join the Beta ⬇️