CloudSlang, the open source tool for orchestrating your development and operations use cases, has just released version 0.9.50. Here are some of the updates, changes and enhancements that were made in this version.

Content

Once again, our new content contains quite a bit of code contributed from the community. Content was added for integrating with VMware, Heroku and Operations Orchestration.

VMware vSphere is a virtualization platform which simplifies IT by separating applications and operating systems from the underlying hardware. The VMware content deals with virtual machines, including flows and operations to create, power on/off, update and delete.

Heroku is a cloud platform based on a managed container system for deploying and running modern apps. The Heroku content deals with accounts, applications, domains, regions and more.

Operations Orchestration is an IT process automation solution designed to increase automation adoption in a traditional data center and hybrid cloud environment. The Operations Orchestration content packages CloudSlang flows and operations as Operations Orchestration content packs.

DSL

The documentation style for flows and operations has been updated to improve readability and include more structure. In addition, system properties files, formerly flat YAML files, have been converted to CloudSlang files with their own syntax and ending with the .props.sl extension. The syntax for accessing system properties has changed to using the get_sp() method.

CLI

The improvements to the DSL are reflected in several enhancements to the CLI as well. The new inspect command can be called with a flow or operation file argument to display the files documentation. Similarly, the new list command can be called with a system properties file argument to display the system properties contained in the file.

The amount of information printed to the screen by the CLI can now be changed using the --v flag. By default, task names and top-level outputs are printed to the screen. By passing the quiet argument only top-level outputs are printed to the screen. And to print task names, top-level outputs and each task’s published variables use the debug argument.

The CLI is now configurable using a configuration file found in the new cslang/configuration folder. The file currently includes configuration for character encoding and the location of the new logging configuration file.

Docker

In addition to our regular Docker image for CloudSlang we have added a dev oriented Docker image that packages tools needed for developing content along with the CloudSlang CLI.

Compiler

Executable files that are valid YAML but not valid CloudSlang, which previously failed in the pre-compilation stage, now pass pre-compilation and all errors are collected.

Learn More

To learn more about the CloudSlang project, visit our website.