Add semi-automated CI stuff

[merlijn-sebrechts]

• Terraform
• Scripts
• Useful overview links

[jnsgruk]

Before this merges, we need to decide what to do with the Terraform state. In my own repos like this, I store the state encrypted in a (free tier) Azure object storage bucket (see here: https://github.com/jnsgruk/infra/blob/a3d5302e9189f45b7abbbaa8667e74d7d2be8494/provider.tf#L9-L14)

You can then provide the secret in CI on merge like this: https://github.com/jnsgruk/infra/blob/a3d5302e9189f45b7abbbaa8667e74d7d2be8494/.github/workflows/deploy.yaml#L25

Without the state file, it'll be much harder for anyone to actually use this :)

[jnsgruk]

I'd prefer to see this array declared with one repo per line, only because when we commit changes the diffs will be much easier to grok :)

[merlijn-sebrechts]

@jnsgruk This might need some discussion. I added the PR mainly for documentation purposes. So snapcrafters can see what I'm using, and so we have something to refer other people to who are interested in automating this.

I don't want to work on how to actually make this usable by other people yet. Do you think it makes sense to commit this as "docs to give you a general idea of what Merlijn is doing to scale himself", or do you think I should put it in another repo or something else?

[jnsgruk]

@merlijn-sebrechts adding it here as docs is a good start, but honestly there isn't much to do to make it automated. We can make that leap another time, but it might get harder to move the state to somewhere central.

[merlijn-sebrechts]

Closing this as I'll upload it to a separate repo. If we ever want to automate this properly, it will have to have specific permissions separate from what this repo provides, so it's better to just immediately add it in its own repo.