Replies: 8 comments
-
confirmed, as we use the default image the software is onboarded. Why should we use it though if tests already use backup to url ? |
Beta Was this translation helpful? Give feedback.
-
They are backing up to someone's Azure subscription. I know they have failed once already because someone had to go in and purge the storage account because we exceeded the file limit for the blob container. |
Beta Was this translation helpful? Give feedback.
-
ah ok, so with the storage emulator we could clean it up "better" ? |
Beta Was this translation helpful? Give feedback.
-
Yes, it would not require cleanup at all if each test run is a new build
server.
If we are using the same image or VM for multiple runs then we just need to
make sure storage space is not consumed.
…On Fri, Mar 8, 2019, 10:01 AM Simone Bizzotto ***@***.***> wrote:
ah ok, so with the storage emulator we could clean it up "better" ?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#5163 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKr2m6glHrOALUQ_aR34iHiCQ0-bf-AXks5vUolSgaJpZM4bkTVu>
.
|
Beta Was this translation helpful? Give feedback.
-
okay, got it! we do not persist storage between builds so it should be all fine and dandy |
Beta Was this translation helpful? Give feedback.
-
k im down |
Beta Was this translation helpful? Give feedback.
-
I'll see if I can work on this this week. I have the emulator on my dev machine so will see if I can get the test to run against it properly. |
Beta Was this translation helpful? Give feedback.
-
This sounds like a fun github action to setup -- it's now called |
Beta Was this translation helpful? Give feedback.
-
Is there any interest in utilizing Azure Storage Emulator for our test with the restore command. The restore command is the only one I can see us actually testing against Azure Storage (backup to URL).
Appveyor confirms they do have the emulator installed for us (or at least it should be). If not we can always just install it ourselves.
The setup is simply getting the emulator initialized and setup on the given server we are testing on for the given instance. This is all documented. I can see in the restore test we are testing on shared access keys which for the emulator is possible but would require us to just put the Az module for the Storage Accounts on the server so we can generate that key. The access key though is documented and known key so there is no security issues in including this in the scripts.
@potatoqualitee // @niphlod // @Stuart-Moore
Beta Was this translation helpful? Give feedback.
All reactions