OpsChain is an API-first orchestration and change automation platform based in GitOps principles with a powerful command-line interface (CLI).
In earlier posts, we introduced you to the OpsChain CLI and demonstrated how to simply create Projects and Environments with OpsChain. We also created our first action definition called echo that prints out the current change context (TL;DR – it prints out the project name and the environment name from the context in which the change was running).
In this post, we will create a change using OpsChain. A change is the the intersection of performing an action in an environment using a specific git revision. We will use the latest commit revision in master to deploy this change to both the dev and test environments using OpsChain.
For those wanting hands-on access and an opportunity to test drive OpsChain with your real-world use cases, we are currently running a pre-release trial with limited spots available. We’d love to get your feedback, and of course there’s some cool swag available for pre-release participants :). To register your interest in participating in the OpsChain pre-release trial, please register at https://opschain.io/#get-access
Happy automating and stay tuned for more updates!