Action Orchestrator 5.0.0 Release Notes

Release Date

First Published: February 16, 2019


  • February 19, 2019: Added the Documentation section to include updated pages.

  • August 1, 2019: Updated the Documentation section to include the updated page.


Action Orchestrator 5.0.0 is available as installer files for ALL components for all supported clouds (see Installer Overview).


Action Orchestrator is a component of CloudCenter Suite which is deployed as containers in a Kubernetes cloud.


The following are the list of features supported by Action Orchestrator:


The following are the list of adapters supported by Action Orchestrator:

  • Data processing and table activities in the Core adapter.

  • Powerful Web Service and Terminal adapter that can integrate with any system that support REST APIs and SSH commands.

  • Built-in integration with AWS Service, Ansible Tower, Email, and Meraki controller.

  • Supports SSH and Python script.

  • Supports JDBC activities on MySQL, Oracle, SQL Server, and SAP HANA databases.

  • Supports custom adapters for easy extension and integration:

    • Allows creating custom adapter templates in 3 programming languages: Golang, Python, and Java.

    • Allows creating custom adapter schema authoring UI for quick proof-of-concept adapters.

Administration and Governance


Refer to the Suite Admin for additional context on Security Considerations.



For API information, see Action Orchestrator API.


The following are the integrations that can performed from the Action Orchestrator 5.0.0:

You need access to the Git files to import the following adapters as atomic workflows in Action Orchestrator. For access, contact CloudCenter Suite Support team.

  • Microsoft Azure

  • VMWare

  • Kubernetes

  • Cisco Digital Network Architecture Center (DNAC)

  • Cisco UCS Director (UCSD)


The following documentation change was implemented in Action Orchestrator 5.0.0:

Known Issues

Action Orchestrator has the following known issues for this release:

  • Currently the table types can be created without columns. The workflow fails to create instances, when table types without columns are used in the workflows.

  • When you add a SSH script node and define a script argument with a space in it, then you attempt to access that script argument by $1 (the first argument).

    • For example, it only returns the first character in the argument list, not your first defined script argument.

      So if your script argument is -e package 'nano' and your ssh script has:

      chef-apply $1

      You will only get chef-apply package sent.


The following documentation changes were implemented in Action Orchestrator 5.0.0:

  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks