Skip to content

[milvus] Ability to use user specified ConfigMap for Milvus configuration #200

[milvus] Ability to use user specified ConfigMap for Milvus configuration

[milvus] Ability to use user specified ConfigMap for Milvus configuration #200

Re-run triggered July 12, 2024 03:09
Status Success
Total duration 7m 8s
Artifacts

lint-test.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
lint-test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, azure/setup-helm@v1, actions/setup-python@v2, helm/kind-action@v1.2.0. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
lint-test
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, azure/setup-helm@v1, actions/setup-python@v2, helm/kind-action@v1.2.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
lint-test
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
lint-test
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/