The playbook is a YAML file that follows a syntax similar to the Ansible playbook syntax. This syntax allows the playbook to run commands in a Windows cmd window using the win_shell module. Sample playbook files can be found in the Ansible git repo.

- name: Configure Fast Web VM
   hosts: all

Perfecto supplies a small set of prepared playbook files:

These can be customized for the particular customer's use case. Alternatively, a custom-playbook can be prepared for the user.

The playbook execution may access files that need to be transferred to the VM during the DCS processing. The files are stored in a partition for the particular customer in a Perfecto, cloud-based, repository. These files will be uploaded by Perfecto support for the customer.

The DCS feature introduces the following new Selenium driver Capabilities:

• customizationScript - identifies the playbook used to configure the Desktop-Web environment. Playbook file should be located in the customer's partition in the Perfecto cloud repository and should be in the format described above.
• customizationScriptArgs - arguments supplied to the playbook. The arguments should be supplied as a Java Map format. The playbook supports two arguments:
  • timeout - defines the timeout for completion of the customization. Integer value indicates the number of seconds [default value: 90 sec]
  • fileslist - a list of String names of artifacts that playbook accesses.

The following snippet uses the capabilities to identify the playbook, and supply a list of files and a new timeout:

Map<String, Object> resourceArgs = new HashMap<>();
resourceArgs.put("timeout", 120);
myfiles =  new String[]{"arg1", "arg2", "arg3"};
resourceArgs.put("fileslist", myfiles);
capabilities.setCapability("customizationScript", "MyPlaybook.yml");
capabilities.setCapability("customizationScriptArgs", resourceArgs);

For a full sample, see the sample in GitHub that pre-loads a set of certificates to the Desktop-Web machine.