Up until now we haven’t done much with the Command Line Interface (CLI) except run a single file. However, the CLI is capable of a lot more.
pumlhorse file1.puml file2.puml file3.puml
.pumlfiles in directory(s):
pumlhorse my_scripts_dir my_other_scripts_dir
.pumlfiles in a directory and all its sub-directories:
pumlhorse my_scripts_dir --recursive
Pumlhorse also supports context files. These are data files that can be accessed by scripts. For instance, it’s common to extract things like server names or connection strings into configuration files.
To run a script with a context file, use the
-c <context_file_name> switch:
pumlhorse myScript.puml -c context.dev.yaml
Conceivably, you would have separate
context.*.yaml files for other environments.
If you run a large number of scripts at a time, you may wish to control how many to run concurrently. For example, you may wish to avoid overloading a website or hanging database connections.
pumlhorse my_big_script_dir --max-concurrent 4 will run all the
.puml files in
my_big_script_dir, but only four at a time.
If you do not specify this, the default value is 15
With this much customizability, using the command line can be overwhelming. Thus, Pumlhorse allows the use of profiles to manage run configurations. A profile is a YAML file that specifies the options above. It must end in the extension “.pumlprofile”. See the full schema here
To run Pumlhorse with a profile, use the following syntax:
pumlhorse --profile my_profile.pumlprofile