add armageddon support

[fitztrev]

No description provided.

[fitztrev]

@ornicar one thing I noticed is that I needed to add at least a 3 second sleep between creating the bulk pairing until I can call add-time on any of its games, otherwise I get a 404.

I'm OK keeping the sleep as long as it's not a possible issue.

here's a minimal repro

#!/bin/bash -e

LICHESS_URL="http://localhost:8080"
ADMIN_API_TOKEN="lip_admin"
WHITE_API_TOKEN="lip_bobby"
BLACK_API_TOKEN="lip_mary"

bulk=$(curl --silent -X POST "$LICHESS_URL/api/bulk-pairing" \
    -H "Authorization: Bearer $ADMIN_API_TOKEN" \
    -d "players=$WHITE_API_TOKEN:$BLACK_API_TOKEN" \
    -d "clock.limit=300" \
    -d "clock.increment=0"
    )

echo "##### BULK PAIRING #####"
echo $bulk | jq .

sleep 3 # <-- this is required, otherwise the add-time returns 404

echo "##### GAMES #####"
gameIds=$(echo $bulk | jq -r '.games[].id')
for gameId in $gameIds; do
    echo "Game ID: $gameId"
    addTime=$(curl --silent -X POST "$LICHESS_URL/api/round/$gameId/add-time/60" \
        -H "Authorization: Bearer $WHITE_API_TOKEN")
    echo "Added time to game $gameId: $addTime"

    echo "$LICHESS_URL/$gameId"
done

[ornicar]

right, because that endpoint only schedules the bulk. It can be in the future, or for "immediate" execution in your case.
But in both case it's scheduled, and in the absence of a date it will just be executed - and the games created - when the scheduler picks it up.

The scheduler runs every 3 seconds

[ornicar]

I used your shcript to confirm that the commit above works.

[ornicar]

can now be removed