Open kimjamia opened 2 years ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @ahmedelnably, @fabiocav.
Author: | kimjamia |
---|---|
Assignees: | - |
Labels: | `Service Attention`, `Functions`, `customer-reported` |
Milestone: | - |
route to service team
It may be the storage endpoint suffix you're using in the initial deployment of the function app, if youre function app has its own storage account. In a test environment, we had core.windows.net
hardcoded but then had an issue going to another environment, and the "404" for a function key update was referring to an internal error finding the container azure-webjobs-secrets
.
We get the same error 'Not Found' when we try to set the masterKey via azure cli.
This does not work and returns Operation returned an invalid status 'Not Found'
az functionapp keys set -g 'RG' -n 'FNAPP' --key-type masterKey --key-name '_master' --key-value 'MYKEY'
Turns out, to set the masterKey you have to set it with the type functionKeys. So this does work:
az functionapp keys set -g 'RG' -n 'FNAPP' --key-type functionKeys --key-name '_master' --key-value 'MYKEY'
Seems wrong to me...
Describe the bug
Possibly related issue: Azure/Azure-Functions#2221
Command Name
az functionapp keys set
Errors:
az functionapp show --name {} --resource-group {}
with the same parameter values works as expected.To Reproduce:
az functionapp keys set --key-type masterKey --name {} --resource-group {} --key-name "_master"
Expected Behavior
A key named
_master
with a generated value was created and assigned to the function app.Environment Summary
Additional Context