Overrides

Cascade uses Ansible playbooks to run jobs. There are standard playbooks that are used, but if advanced customizations are needed then playbook overrides can be used to satisfy those needs. Overrides can be put in place on a per environment or per project basis depending on your specific needs, and they can be applied for code, asset, or database jobs.

Examples

One example of an override that can be used is one that installs composer on code deployments. This can be used instead of using a script action.

- name: Run Composer Install
  shell:
    cmd: COMPOSER_ALLOW_SUPERUSER=1 COMPOSER_MEMORY_LIMIT=-1 composer install --no-interaction --optimize-autoloader --no-dev
    chdir: "{{ deploymentPath }}"
  when: composer_stat_result.stat.exists
  ignore_errors: true

Another example of an override that can be used is one that applies special permissions in your environment.

- name: Set permissions
  shell:
    cmd: chown -R 123e:apache .
    chdir: "{{ deploymentPath }}"

These are just a few examples of overrides that can be used for Cascade. Overrides need to be applied by our Contegix team as they exist on the Cascade server specifically. If you’re interested in discussing potential override options for your environment, our support department would be happy to discuss those needs with you. To submit a support ticket, please visit https://service.contegix.com.