Fail to create a Slot with KeyVault reference

[mortezasoft]

While trying to create a new Slot, I faced this issue.

WEBSITE_CONTENTAZUREFILECONNECTIONSTRING config is using @Microsoft.KeyVault reference and function is consumption based.

Repro steps:

1. use @Microsoft.KeyVault in WEBSITE_CONTENTAZUREFILECONNECTIONSTRING config in an azure function app.
2. try to create a new Slot.

Action: azureFunctions.createSlot
Error type: BadRequest
Error Message: The parameter 'WEBSITE_CONTENTAZUREFILECONNECTIONSTRING' has an invalid value. Details: Cannot specify key vault references not referencing User Assigned Identity on Create Site.

Version: 0.20.2
OS: darwin
Product: Visual Studio Code
Product Version: 1.42.1
Language: en

Call Stack

extension.bundle.js:218:2910489
s extension.bundle.js:218:111756
s extension.bundle.js:164:25792
extension.bundle.js:164:27036
o extension.bundle.js:164:674848
extension.bundle.js:164:24705
$._callback extension.bundle.js:1:635041
$.t._callback.t.callback.t.callback extension.bundle.js:194:5590
$.emit events.js:200:13
$.<anonymous> extension.bundle.js:194:18450
$.emit events.js:205:15
IncomingMessage.<anonymous> extension.bundle.js:194:17282
Object.onceWrapper events.js:288:20
IncomingMessage.emit events.js:205:15
endReadableNT _stream_readable.js:1154:12
processTicksAndRejections task_queues.js:84:9

[ejizba]

Just to clarify - does the keyvault reference work normally? It's just the slot that has the problem?

I'm 99% sure the VS Code extension is just passing this error along directly from Azure. You might have better luck trying to get support from the Azure platform team directly, either through support in the portal or one of these options: https://github.com/Azure/Azure-Functions#questions--help

[mortezasoft]

Thanks @EricJizbaMSFT! Yes it's working normally and I believe you are right and it's coming directly from Azure. The new Slot can not be created due to some issues as long as @Microsoft.KeyVault reference is used.

[ejizba]

Okay I have enough information to look into it - but you might want to follow up with the above mentioned support options if you want a quicker fix

[mhoeger]

@EricJizbaMSFT - I believe the root cause is being tracked here: Azure/azure-functions-host#5306

Assuming this is the same issue, this is being fixed on the platform side although it won't be deployed for a little bit

[callppatel]

Do we know when it is going to be fixed?