---
- hosts: aws_node_local
  become: true

  vars:
    # See group_vars/aws_node_local.yml, which pull vars from the environment.
    atl_product_family: "stash"
    atl_product_edition: "mesh"
    atl_product_user: "bitbucket"
    atl_product_home: "{{ atl_home_base }}/{{ atl_product_edition }}"
    atl_systemd_service_name: "mesh.service"
    atl_startup_systemd_params:
      - 'UMask=0027'
      - 'Environment=MESH_HOME={{ atl_home_base }}/{{ atl_product_edition }}'
      - 'Environment=JAVA_HOME=/usr/lib/jvm/java'
      - 'Environment=JRE_HOME=/usr/lib/jvm/java'
      - 'Environment="JVM_SUPPORT_RECOMMENDED_ARGS=-Dmesh.enabled=true -Dplugin.bitbucket-git.mesh.sidecar.child-process=false -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath={{ atl_home_base }}/{{ atl_product_edition }}/log"'
      - 'Environment=JVM_MAXIMUM_MEMORY={{ atl_jvm_heap }}'
      - 'PassEnvironment=JAVA_HOME'

    atl_startup_exec_path: "{{ atl_product_installation_base }}/current/bin/start-mesh.sh"
    atl_stop_exec_path: "{{ atl_product_installation_base }}/current/bin/stop-mesh.sh"
    atl_systemd_service_target: "multi-user.target"
    atl_startup_exec_options: []

  roles:
    - role: linux_common
    - role: aws_common
    - role: aws_shared_fs_config
    - role: product_common
    - role: product_install
      tags: [skip_on_stack_update]
    # startup before config here so that the handlers from each role are
    # executed in the right order at the end of the play; only task in startup
    # is to create the systemd service file, so this should have no ill effects
    - role: product_startup
    - role: bitbucket_mesh_config