Version 3.3.0

This release contains a new feature for Hypernode Brancher deployments.

It was already possible to clean up Brancher instances by running hypernode-deploy cleanup. This looked at the deployment-report.json file to see which instances were created an cancelled them. While this is a nice and fundamental feature to have, we found that we still missed something.

What we felt that was missing was a way to cancel Brancher instances not for just the current run, but for all Brancher instances created for a given pull request. For this to happen, you need to label the Brancher instances in the deploy.php file:

$configuration = new ApplicationTemplate\Magento2(['en_US', 'nl_NL']);

$productionStage = $configuration->addStage('test', 'myshop');
$productionStage->addBrancherServer('example')
    ->setLabels(['gitref=' . (\getenv('GITHUB_HEAD_REF') ?: 'unknown')]);

return $configuration;

With this configuration, the test stage will create a Brancher instance with the label gitref=my_feature_branch.

When you want to clean up instances based on that gitref, you can simply run the cleanup command like this:

hypernode-deploy cleanup test

This will look up the Brancher instances using the Hypernode API and match the brancher instances by the labels configured for the test stage.

What's Changed

• remove old 'build image locally' from readme by @vdloo in #62
• add instructions to build and run local image by @vdloo in #63
• Create Brancher node with provided labels and settings by @tdgroot in #65
• Cleanup Brancher nodes by labels by @tdgroot in #66

Full Changelog: 3.2.0...3.3.0