Add more "acceptable errors" on repo initialization

[jessebot]

Summary

This is to fix this issue: #690

We currently only check for "already intitialized", but in the restic backend for backblaze b2, they also throw "config already exists" as a possible error for the same thing. Because both errors are possible and probably fine, I created an array, in case more show up in the future, for easier fixing.

Checklist

• Keep pull requests small so they can be easily reviewed.
• Categorize the PR by setting a good title and adding one of the labels:
  bug, enhancement, documentation, change, breaking,
  as they show up in the changelog
• Update the documentation.
• Update tests.
• Link this PR to related issues.

[jessebot]

Closing because tests failed locally and I need to take a further look at this on my end before bothering maintainers. Sorry for the clutter.

[jessebot]

Just need someone to take a peek and then I can take a peek at #563 as well, because it still shows up in tests, but happens before my fix as well.

Note: the e2e tests were not successful when I cloned master, so I've ignored them in testing this fix and instead tested directly with the method below.

I haven't tested restoring from backups yet, but I did test both schedules (on a two minute cron schedule) and backups (just deleting and reapplying the backup resource) and they're completing/marked as succeeded, as well as I checked backblaze b2 and the data is being updated. My testing was just running make docker-build/make docker-push with a modified Makefile to push to a local docker repository running inside a small KIND cluster, and then doing a helm upgrade with a values.yaml that changed the k8up image params to my local kind docker repo images. It failed on the changes from 3 days ago, but works on the most recent change I've pushed up to this branch in my forked repo.

EDIT: wrong issue, fixed to correct issue number, typos

[Kidswiss]

hi @jessebot

I've triggered the pipeline here and the E2E tests seem to succeed.

Were you able to verify, that this works with B2? If so this looks good to me.

[jessebot]

Yep, works with b2 for backups and schedules. Tested with annotated application aware backups for postgresql pvc.

[Kidswiss]

LGTM

[Kidswiss]

@jessebot thanks for your contribution! 🎉