Conversation
2686323 to
19d3449
Compare
|
@pchovelon & @OrioQuezac could you review this one even if it's still a draft ? I would like some feedback before adding the doc and a few more tests. I think it could be great to test it for real. |
0373789 to
5325ffd
Compare
|
related to #61 |
5715ce7 to
4b0991b
Compare
This is a first step to handle more backend storage and their secret names/logic.
When converting slices of structs to environment variables, fields with the same nestedTag now share the same counter. This ensures that numbering continues between different slices instead of restating the counter. This will make possible to handle different slices for different type of repository (e.g. one slice for s3 repo and another one for Azure). E.g. with 2 different slice, we will have PGBACKREST_REPO1_S3... PGBACKREST_REPO2_S3... PGBACKREST_REPO3_AZURE...
4b0991b to
33cbb6a
Compare
33cbb6a to
0d799c2
Compare
| t.Fatal("pod not ready") | ||
| } | ||
|
|
||
| b := takeBackup(ctx, t, k8sClient, NS, clusterName, "azure-backup-01", p) |
There was a problem hiding this comment.
We may remove `takeBackup() of this test and create a new test name CreateAndRestoreFromAzure() or something like this.
This new test will test the entire "lifecycle" Create -> Backup -> Delete -> Restore.
There was a problem hiding this comment.
I won't do that until we have reduced the duration of the test.
There was a problem hiding this comment.
btw, i think we can refactor and share some code between the TestCreateAndRestoreInstance for S3 and Azure tests. It should be done after improving the tests duration and probably before integrating another backend storage.
fa24c07 to
e0effd8
Compare
No description provided.