L Suarez

Results 11 comments of L Suarez

@liliankasem Is there any public location to track release milestones for defects like this so I can keep an eye out? This issue has been plaguing me for some time...

@nzthiago @liliankasem This seems to have gotten worse recently. The workaround of disabling the storage account firewall settings to allow public access, performing the swap, and restoring it after the...

> Thank you for the follow-up, @nzthiago. I'm going to work through some testing this evening to find out exactly what state we're in. Unfortunately, the BICEP deployments in question...

@nzthiago I've attempted any number of firewall and network configurations to see if I could successfully complete a swap. However, all of them have reported the same response below when...

Thanks for the follow-up @nzthiago. At this point we're back to previous state and awaiting the deployment of this fix to my scale unit. The previous workaround is allowing swaps...

> This is still available, but I'm not sure if this other could be related covering this one #4694 @tomkerkhove ? I'm also very interested in this issue as I've...

Adding screenshot capture of delta in behavior in production environment. Working example 21 Feb 23 ![image](https://user-images.githubusercontent.com/12800602/221958114-5e1779e3-2a51-4bc7-96eb-44bd5b0aba4d.png) Changed behavior the following evening 22 Feb 23. No code deployment was performed in...

> Hi @mikeholdorf, Could you please let me know if you are still seeing same behavior(outut content-type as 'application/octet-stream') for built-in blob connector action 'Upload to storage container'? @saroja-sattigeri Hi....

@saroja-sattigeri I'm outputting our runtime settings below, but development and production environments have configuration parity. ``` [ { "name": "AzureFunctionsJobHost__extensionBundle__id", "value": "Microsoft.Azure.Functions.ExtensionBundle.Workflows", "slotSetting": false }, { "name": "AzureFunctionsJobHost__extensionBundle__version", "value": "[1.*,...

@saroja-sattigeri The output of the production HTTP response body we're writing to blob is the correct Content-Type. ``` { "statusCode": 200, "headers": { "Cache-Control": "no-cache", "Pragma": "no-cache", "Date": "Wed, 15...