# Using Ansible 2.10.0a1 under Azure there might happen that the output of a
# task is changed if a module uses no_log = True for an attribute.
#
# For example, if the output of the module should contain "changed: True", and
# an attribute with no_log set contains the value `hang` it might happen that
# the output is modified to "c******ed: True", and if this output is further
# processed (registering the result and comparing the value of `changed`),
# the test might fail, but not because of module code, but because of unexpected
# output processing.
#
# This behavior was, currently, only reproduced with Ansible 2.10.0a1 running
# under Azure.
---
trigger:
- master

pool:
  vmImage: 'ubuntu-18.04'

jobs:
- job: RunLinters
  displayName: Run Linters
  steps:
  - task: UsePythonVersion@0
    inputs:
      versionSpec: '3.6'

  - script: python -m pip install --upgrade pip setuptools wheel
    displayName: Install tools

  - script: pip install pydocstyle flake8
    displayName: Install dependencies

  - script: flake8 .
    displayName: Run flake8 checks

  - script: pydocstyle .
    displayName: Verify docstings

- template: templates/playbook_tests.yml
  parameters:
    group_number: 1
    number_of_groups: 3
    build_number: $(Build.BuildNumber)

- template: templates/playbook_tests.yml
  parameters:
    group_number: 2
    number_of_groups: 3
    build_number: $(Build.BuildNumber)

- template: templates/playbook_tests.yml
  parameters:
    group_number: 3
    number_of_groups: 3
    build_number: $(Build.BuildNumber)