I am wondering if anyone has integrated Make with GitHub and used it to upgrade/downgrade scenarios in a dev/stage/production type of environment. We use the Make API to clone and configure scenarios in make for AccountBridge, but we’d like to also perform change management via GitHub on our suite of scenarios.
Our early thoughts look like this but I’d love to hear what others have done:
- Checkin all our current actively used MASTER scenarios into the
accountbridge-backendrepo on github (use a accountbridge-make-blueprints folder) - When of scenarios are updated for some reason, create a feature branch with the updated blueprints, and commit the blueprints JSON to the feature branch like any other code.
- We will need to have a set of master templates in Make for our dev/stage/prod environments to allow a change management process to occur just like our code currently does. So there’s a development set of scenarios, a stage set and a prod set. Create the necessary structure in MASTER team via make folders.
- When a PR is merged into a “dev”, “stage” or “prod” branch of our backend repository, a GitHub Action will also see if scenarios need an update based on the merged scenario blueprints, and which environment they are affecting. The GitHub Action will “archive and upgrade” the scenarios on our “master template” team in our AccountBridge Make instance taking into account the dev/stage/prod environments. The make-cli can be used via an npm module.
Previous scenarios will be archived in make. New scenarios each with its own version number will pushed into the master template team into the correct folder.
The code on the accountbridge-backend will need to point to the correct folder so some related changes may need to be made there as well.