fix: QnA Maker EndpointKey is null Issue #1571
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR is to fix this Issue
Ref
Root Cause
This Issue is because the botproject(runtime) read qna.endpointkey from disk before, and we omit it as a fixed sensitive property. But It's more like a self-defined property and no need to omit.
Task Item
closes #1538
Type of change
Please delete options that are not relevant.
Checklist
Screenshots
During the QnaMaker trace, it won't show "Object not set to instance of an object" anymore.
