Thanks for the video. 15m30s - "Access keys never expire" - they don't expire as such inasmuch as they don't have an expiry date like SAS tokens do but they could be rotated, thereby making previous keys unusable
31m50s - wouldn't you need the MKDIR command to run every time the VM starts after being de-allocated? That is, not just at the time BlobFuse is initially configured?
I think you might be right, I think I'll need to make sure that the folder is created every time the machine reboots. I'll have to check on that as blobfuse might create the directory automatically as well.
Me again (sorry). Regarding getting the Storage Account + Container names into the BlobFuse script (and the steps that entailed) - wouldn't it have been somewhat easier to explicitly specify the SA name rather than have it randomised? Then you wouldn't have needed all those extra steps?
good question. Storage Accounts are notoriously hard to name given they need to be globally unique and are very short (29 characters). Hence, rather than trying to get my naming conventions to conform to what storage account names are available, I just punt and make my storage accounts have inherently random names. This then requires me to dynamically link things together but that is also a good practice anyway. I wouldn't want to hard code the storage account name inside a packer image. So the VM extension is a good place to inject the actual storage account name into the placeholder in the blob fuse config. At that point, it doesn't matter if the name is randomized or hard coded, its still being injected via terraform using the Virtual Machine Extension.
Thanks for the feedback. I have noticed that I tend to bang on my desk. Lol. But also my mic picks up my heavy typing as well. I’m looking into other options where the mic is more insulated from vibrations like that.
Thanks for the video. 15m30s - "Access keys never expire" - they don't expire as such inasmuch as they don't have an expiry date like SAS tokens do but they could be rotated, thereby making previous keys unusable
That's true. They can be explicitly revoked but, in my mind, that's different from 'expiring'.
31m50s - wouldn't you need the MKDIR command to run every time the VM starts after being de-allocated? That is, not just at the time BlobFuse is initially configured?
I think you might be right, I think I'll need to make sure that the folder is created every time the machine reboots. I'll have to check on that as blobfuse might create the directory automatically as well.
Me again (sorry). Regarding getting the Storage Account + Container names into the BlobFuse script (and the steps that entailed) - wouldn't it have been somewhat easier to explicitly specify the SA name rather than have it randomised? Then you wouldn't have needed all those extra steps?
good question. Storage Accounts are notoriously hard to name given they need to be globally unique and are very short (29 characters). Hence, rather than trying to get my naming conventions to conform to what storage account names are available, I just punt and make my storage accounts have inherently random names. This then requires me to dynamically link things together but that is also a good practice anyway. I wouldn't want to hard code the storage account name inside a packer image. So the VM extension is a good place to inject the actual storage account name into the placeholder in the blob fuse config. At that point, it doesn't matter if the name is randomized or hard coded, its still being injected via terraform using the Virtual Machine Extension.
i think you may want to fix your mic, its very sensitive and loud when you slightly hit the table.
Thanks for the feedback. I have noticed that I tend to bang on my desk. Lol. But also my mic picks up my heavy typing as well. I’m looking into other options where the mic is more insulated from vibrations like that.