-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add "Did You Mean This" Extension #1692
Merged
fengzhou-msft
merged 36 commits into
Azure:master
from
christopher-o-toole:thoth-extension
May 15, 2020
Merged
Add "Did You Mean This" Extension #1692
fengzhou-msft
merged 36 commits into
Azure:master
from
christopher-o-toole:thoth-extension
May 15, 2020
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…istory/readme info.
…ecommendations aren't available and/or the user has an outdated CLI.
…pathing to recommendation file.
…ookup table logic for now.
…s, add Aladdin style parameter placeholders, remove lookup table references, resolved issue with generated recommendations.
… async update check, clean up integration and unit tests, rely only on pip for versioning.
…. Add some tests to verify normalization.
…gs. Expand command test suite to include a range of commands.
…mmendation model, add base class for aladdin test logic.
… check if telemetry is enabled, add more comments, enable automated test support for user fault command failures and extension metadata, add mock recommendation model file.
…rt_parameters function, remove number of pairs entry from mock recommendation file.
…r static analysis, order imporrts better, remove deprecated parameters from `kusto cluster create` test case, fix global param rules.
If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
|
add to S170 |
jiasli
approved these changes
May 14, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
haroldrandom
approved these changes
May 14, 2020
fengzhou-msft
approved these changes
May 14, 2020
fengzhou-msft
approved these changes
May 15, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Replacing the previous PR #1536
New extension (in preview) which uses the Aladdin service to generate and show failure recovery recommendations on command failure. This extension makes use of the hook added to
parser.py
in CLI version2.4.0
. For more information, see this CLI PR.This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines
azdev style <YOUR_EXT>
locally? (pip install azdev
required)python scripts/ci/test_index.py -q
locally?For new extensions:
About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update
src/index.json
automatically.The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify
src/index.json
.