Runs an Ansible galaxy requirements file. This operation takes a name or path of the specific requirements file as well as any desired arguments and install the roles.
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Ansible Home |
| No | Absolute directory path where Ansible is installed. |
Ansible Requirements File |
| No | Absolute or relative path to Ansible galaxy requirements YAML file. If the yml file is in the artifacts directory, you do not have to pass anything in this field Absolute Path Example: /home/ubuntu/ansibleTest/requirements.yml Relative Path Example: ansibleTest/requirements.yml |
Extra Variables |
| No | Additional variables as key=value, JSON text, or a JSON/YAML file. Formatted as key=value. If passing a JSON/YAML file, you must use an @ before the file name. One pair per line (CLI arg: -e) Key/Value Example: var1=val1 var2=val1" JSON Example: {"version":"1.23.45","other_variable":"foo"} JSON/YAML File Example: @some_file.json |
Additional Arguments |
| No | Additional CLI Arguments that you want to add. |
Artifacts
This operation delegates consumes/produces artifacts decision to the workflow developer. Check Consumes Artifacts on the workflow step editor if this operation requires artifacts to be delivered prior to execution of the script. Check Produces Artifacts on the workflow step editor if this operation creates artifacts. The artifacts folder is available via the FD_ARTIFACTS_DIR variable.
...