playing with multiline commands in ansible

ansible_multiline.yaml

#! /usr/bin/env -S ansible-playbook --inventory=localhost, -v
# execute me by running `./multiline_commands.yaml`
---
- name: Playground
  hosts: localhost
  connection: local
  gather_facts: no
  tasks:
    - name: >
        multiline command don't need `\` because
        (I think) `command` implicates everything in the
        key belongs to one command and could never be
        interpreted as many commands unlike `shell`
      command: |
        date
          --utc

    - name: >
        multiline shell needs `\` when using `|` so that ansible can
        destinguish where another command starts (without `\` that would
        not be possible)
      shell: |
        date \
          --utc
        pwd