Skip to main content

Orchestrator

The orchestrator has 2 main phases, each with a separate powershell command.

Validation​

This phase will check your specification files and ensure the following:

  • Dependencies. Any object reliant on another will be checked to ensure it either exists currently in your infrastructure or is included in the supplied specification.
  • Mandatory fields. Any mandatory fields which you have not supplied will be highlighted.
  • Field lists. Any field which supports a given list of options will be validated to ensure the value is an accepted value.

Example to validate a single deployment file containing all settings and resource objects.

Confirm-JPResource -Type all -Specification "myspec.yml"

Example to validate multiple deployment files in a single directory collectively containing all settings and resource objects.

Confirm-JPResource -Type all -SpecificationDir "c:\myspecfiles"

Deployment​

This phase will deploy the infrastructure contained in the specification.

Example to deploy multiple deployment files collectively containing all configuration and resource objects. Use separate common files for Setting, Connection and even Variable is a great way to start to modularise your deployments.

Deploy-JPResource -Type all -Specification 'setting.yml','connection.yml','resources.yml'

Parameters​

The following parameters can be used with either command.

ParameterTypeValuesNotes
TypeListAll, SpecificationsResource short codes you wish to deploy, useful to specify a subset of a specification
OutputLogFileStringlog filename for verbose output logging
VerboseSwitchoutput additional verbose information
DebugSwitchoutput additional debug information
InformationActionStringSilentlyContinue (D), Continueoutput additional informational messages