-
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
[containerapp] az containerapp service milvus: Add support for milvus dev service #6863
[containerapp] az containerapp service milvus: Add support for milvus dev service #6863
Conversation
|
rule | cmd_name | rule_message | suggest_message |
---|---|---|---|
containerapp service milvus | sub group containerapp service milvus added |
Hi @bgashirabake, |
Thank you for your contribution bgashirabake! We will review the pull request and get back to you soon. |
az containerap service create |
Recommend title: [containerapp] |
@zhoxing-ms could you please take a look. thank you. |
…r milvus dev service (Azure#6863)" This reverts commit d6d11c9.
Can we reopen this PR given it was reverted and we need to have Milvus CLI ready for Ignite? |
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
General Guidelines
azdev style <YOUR_EXT>
locally? (pip install azdev
required)python scripts/ci/test_index.py -q
locally? (pip install wheel==0.30.0
required)For new extensions:
About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update
src/index.json
automatically.You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify
src/index.json
.