#Termius private key how to
#Termius private key update

The instructions in this section demonstrate how to set up simple functional tests for Terminus plugins using Bats, the Bash Automated Testing System. Automated tests give prospective new users the assurance that the plugin works, and provides a basis for evaluating changes to the plugin. Testing PluginsĪdding automated testing is an important step to take before distributing plugins. If you do change compatible-version, please make sure that your constraint expression does not accidentally include the next major version of Terminus. You can use the standard composer version constraints syntax. If your plugin has a minimum required version of Terminus, you can specify that in the compatible-version section of composer.json. We recommend following semantic versioning when versioning your plugins, just as Terminus does. More information on Terminus standards can be found at: Ensure for compatibility with PHP 5.5, 5.6 and 7.While not strictly necessary, if you plan to distribute your plugin, and especially if you plan to add an open source licence and encourage contributions, it may be a good idea to adopt the Terminus core standards. Terminus 3 does not have this restriction. That means that you cannot use any external classes in your plugin's constructor. In order to avoid conflicts between the dependencies of different plugins, Terminus 1 and 2 do not load a plugin's external libraries until immediately before one of its commands is executed. Your composer file should now look like this:

#Termius private key update

Update the composer.json file with a require section that lists all of the external projects you need, along with their version constraints. If your plugin can still function without its external classes, then you may keep the compatible-version at ^1.

You should also update your plugin's Terminus compatible-version entry to ^1.1, so that older versions of Terminus will not attempt to use it.

This is done by adding your plugin requirements to the require section of your composer.json file, as usual. Starting with Terminus version 1.1.0, it is possible for plugins to depend on external libraries. Remember to change my-username and Pantheon in the above to your vendor name.