grim/convey

Port from logrus to log/slog
default tip
4 months ago, Elliott Sales de Andrade
c588f9b3f559
Port from logrus to log/slog

This doesn't really take much advantage of structured logging beyond what is already done (`id` and `idColor`), and consequently the log handler does not try to do any handling of anything more than that (i.e., grouping, or arbitrary attributes beyond those defined).

One should maybe have a `Context` available to pass in, but there isn't one, and anyway, the log handler doesn't use it, so I've passed in a `TODO` instead.

Everything else is just normal import/rename changes.

Testing Done:
Ran `go run . run`

Reviewed at https://reviews.imfreedom.org/r/2871/
---
tasks:
import:
type: docker/import
files:
- .:.
clean:
type: convey/clean
files:
- convey-docs.zip
- site
# we explicitly call out jinja2==3.0.3 because 3.1.0 breaks mkdocs
# https://github.com/mkdocs/mkdocs/issues/2799
build:
type: docker/run
image: docker.io/python:3-alpine
workdir: ${CONVEY_WORKSPACE}
script:
- set -ex
- python3 -m pip install mkdocs jinja2
- mkdocs build
- apk add --no-cache zip
- mkdir t # we need to use a temporary directory as we may have a convey executable in the workspace
- mv site t/convey
- cd t
- zip -9r convey-docs.zip convey
export:
type: docker/export
files: t/convey-docs.zip:convey-docs.zip
plans:
default:
stages:
- tasks:
- clean
- tasks:
- import
- build
- export
clean:
stages:
- tasks:
- clean