Otter Documentation


  • Last Modified: 2019-07-18

Assets make it easier to automate your infrastructure by leveraging existing scripts and files to create Configuration and Orchestration Plans and scale up.

Moreover, you can restrict access to your assets by creating Rafts in various Environments to restrict access to specific environments. This helps maintain and enhance compliance and security, and helps you build on the existing knowledge, tools, and scripts you have already invested in.

PowerShell and Shell Scripts

Otter's Tight PowerShell and Scripting Integration makes it easy to use your current scripts to automate your current infrastructure. Once you've added a PowerShell or Shell script as an asset, you can call it as an operation in a Configuration or Orchestration plan, and Otter will execute those scripts on the appropriate server, and store logs about their execution.

Module Plans

Modules are reusable Plans that can be called from another plan, or another module, as if it were an Operation. Like other plans, modules are created using the Otter Visual Mode Editor or OtterScript, and consist of Blocks. Module's reusability allows for quick plan creation, and greater accuracy, by using known configuration pieces.

Modules can be useful to spin up generic Servers for rapid testing in the cloud, such as a generic modules to create an AWS Server for short testing periods, or to create segments of configuration plans that will be used across different Server Roles.

Other Files

Otter can store any file type that a server might need for configuration, such as SSL certificates, read-me text documents, license key files, etc. You can even store your pictures of Otters Who Look Like Benedict Cumberbatch.

These files can be deployed or ensured using the Get Asset and Ensure Asset operations.

Is this documentation incorrect or incomplete? Help us by contributing!

This documentation is licensed under CC-BY-SA-4.0 and stored in GitHub.

Generated from commit efc6666b on master