-
Notifications
You must be signed in to change notification settings - Fork 2k
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
mgmt, update test on MongoCluster #41908
Conversation
API change check API changes are not detected in this pull request. |
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.
No client secret allowed.
/azp run prepare-pipelines |
Azure Pipelines successfully started running 1 pipeline(s). |
I'm not seeing mgmt test pipeline being created. |
I also find it a bit strange. Analyzing from the execution log of |
I'm not sure, But I believe we should fix it before merging the PR. Maybe there's a bug in the script. |
/azp run prepare-pipelines |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - mongocluster - mgmt - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
@weidongxu-microsoft @XiaofeiCao |
/azp run java - mongocluster - mgmt - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
* mgmt, update test on MongoCluster * remove output AZURE_CLIENT_SECRET. * Add `UseFederatedAuth: true` to `tests.mgmt.yml` * Update live test case name to `testCreateMongoCluster`.
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines