[Backport 1.x] Add Service Monitor Resource #859
VILJkidAnnotations
20 errors and 8 warnings
|
lint-test (1.19.16):
charts/opensearch/values.yaml#L174
[comments] too few spaces before comment
|
|
lint-test (1.19.16):
charts/opensearch/values.yaml#L528
[key-duplicates] duplication of key "serviceMonitor" in mapping
|
|
lint-test (1.19.16)
Process completed with exit code 1.
|
|
lint-test (1.21.14)
The job was canceled because "_1_19_16" failed.
|
|
lint-test (1.21.14):
charts/opensearch/values.yaml#L174
[comments] too few spaces before comment
|
|
lint-test (1.21.14):
charts/opensearch/values.yaml#L528
[key-duplicates] duplication of key "serviceMonitor" in mapping
|
|
lint-test (1.21.14)
Process completed with exit code 1.
|
|
lint-test (1.24.7)
The job was canceled because "_1_19_16" failed.
|
|
lint-test (1.24.7):
charts/opensearch/values.yaml#L174
[comments] too few spaces before comment
|
|
lint-test (1.24.7):
charts/opensearch/values.yaml#L528
[key-duplicates] duplication of key "serviceMonitor" in mapping
|
|
lint-test (1.24.7)
Process completed with exit code 1.
|
|
lint-test (1.23.12)
The job was canceled because "_1_19_16" failed.
|
|
lint-test (1.22.9)
The job was canceled because "_1_19_16" failed.
|
|
lint-test (1.22.9):
charts/opensearch/values.yaml#L174
[comments] too few spaces before comment
|
|
lint-test (1.23.12):
charts/opensearch/values.yaml#L174
[comments] too few spaces before comment
|
|
lint-test (1.22.9):
charts/opensearch/values.yaml#L528
[key-duplicates] duplication of key "serviceMonitor" in mapping
|
|
lint-test (1.23.12):
charts/opensearch/values.yaml#L528
[key-duplicates] duplication of key "serviceMonitor" in mapping
|
|
lint-test (1.22.9)
Process completed with exit code 1.
|
|
lint-test (1.23.12)
Process completed with exit code 1.
|
|
lint-test (1.25.2)
The job was canceled because "_1_19_16" failed.
|
|
lint-test (1.19.16)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, azure/[email protected], actions/setup-python@v2. 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 (1.19.16)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, azure/[email protected], actions/setup-python@v2. 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 (1.19.16)
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 (1.21.14)
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 (1.24.7)
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 (1.23.12)
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 (1.22.9)
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 (1.25.2)
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/
|