Dan Harris comments

Results 16 comments of


                                            Dan Harris

Output Files from Batch Task to Azure Blob Storage - be able to set content-MD5 as true, so metadata value is automatically set while uploading blobs

This is currently possible through the UploadHeaders parameter of OutputFileBlobContainerDestination. Documentation here: https://learn.microsoft.com/en-us/dotnet/api/microsoft.azure.batch.outputfileblobcontainerdestination?view=azure-dotnet

Output Files from Batch Task to Azure Blob Storage - be able to set content-MD5 as true, so metadata value is automatically set while uploading blobs

Assuming content md5 isn't determinable before hand when you define the output file, this can probably be looked into as a feature request to do it dynamically on upload.

Setting a slot size for Jobs causes them to be run out of order

I believe that ask execution does not have any guaranteed order unless you specifically set dependencies, @bwatrous can perhaps confirm.

Unable configure managed identity while using powershell script to automate pool creation through Azure Pipeline

@dpwatrous Is this a case where PowerShell uses an API that doesn't support managed identity?

Pool fails - authorization to perform action 'Microsoft.Batch/batchAccounts/pools/write'

How are you authenticating locally when you interact with Batch API? Given the error from Azure Container App (permission error) it seems like you are probably authenticating with two different...

Bicep/ARM Template PropertyCannotBeUpdated

Confirmed this is a known issue with the owning team, they are tracking it internally. Will update this thread accordingly

Exit Code 126 / "Permission denied" on Low-Priority Nodes

@FridoDeluxe Thanks for the report! I've seen one other report similar to this come my way but there were no logs for us to search. I'll take a look next...

Exit Code 126 / "Permission denied" on Low-Priority Nodes

I've downloaded and attached logs to our internal tracking board, feel free to remove for privacy reasons.

`ContainerInvalidSettings` when using `--pull=always`

I just checked the sources and it is indeed not parsed which is generating the error. I will check with the author if this was on purpose. I suspect it...

`ContainerInvalidSettings` when using `--pull=always`

Ah ok, this makes sense as the way the implementation currently works is to just check locally for the container image, and if it doesn't exist pull it. Your use...