You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just a note that function apps do not parameterize their key values in the ARM template so hard to deploy to multiple environments. Not sure what the plan is but today, this makes a mess of CICD because there is no easy way to override the functionAppUrl or the functionKey values in the ARM template. Maybe add a caution box in the doc above until this is fixed.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: 1e22e4d6-366f-fbf8-e141-8905ca7ab7ae
Version Independent ID: 5be2acf2-66e7-cadf-6666-5a85a65b9771
@MarkAtAgilliance There were a few changes done recently on Function Apps because of which parameterizing key values in ARM templates was affected. To read more about this, please refer this article. The product team is working on rectifying it and it should be done soon.
There's a workaround however to get you unblocked for now. Here is a sample to inject a default functions key in a key vault secret (Ref :#3994) :
I will now proceed to close this issue. Please feel free still to comment and tag me if you have any queries or ideally provide your feedback on a doc pertaining to Function apps.
Just a note that function apps do not parameterize their key values in the ARM template so hard to deploy to multiple environments. Not sure what the plan is but today, this makes a mess of CICD because there is no easy way to override the functionAppUrl or the functionKey values in the ARM template. Maybe add a caution box in the doc above until this is fixed.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: