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
Describe the bug
When exporting the CognitiveServices/accounts resource in Azure, the validate runner fails because the value of the property qnaAzureSearchEndpointKey is null. The Whatif deployment does not allow this to be null and fails.
This issue happens to the resource type:
"Microsoft.CognitiveServices/accounts",
Steps to reproduce
Pull the resources from Azure
Validate the resources by using a Whatif deployment
Screenshots
The text was updated successfully, but these errors were encountered:
Thank you for reporting this!
We are striving to support all resource providers in pull, but also rely on that the RPs return all the correct schema.
We are currently working on improving this to enable higher quality, but for now, it is best effort.
Out of curiosity, in this particular case, do you always run a validate after pull, or is this after changing the resource through a PR?
Describe the bug
When exporting the CognitiveServices/accounts resource in Azure, the validate runner fails because the value of the property qnaAzureSearchEndpointKey is null. The Whatif deployment does not allow this to be null and fails.
This issue happens to the resource type:
"Microsoft.CognitiveServices/accounts",
Steps to reproduce
Screenshots
The text was updated successfully, but these errors were encountered: