ci: fix linkcheck for graylog (#173)
All checks were successful
continuous-integration/drone/push Build is passing
All checks were successful
continuous-integration/drone/push Build is passing
This commit is contained in:
parent
1d896d21d9
commit
f8f43dff54
@ -45,7 +45,7 @@ steps:
|
|||||||
- name: link-validation
|
- name: link-validation
|
||||||
image: thegeeklab/link-validator
|
image: thegeeklab/link-validator
|
||||||
commands:
|
commands:
|
||||||
- link-validator --color=always --rate-limit 10 -e https://matrix.to/.* -e https://www.graylog.org/.*
|
- link-validator --color=always --rate-limit 10 -e https://matrix.to.* -e https://www.graylog.org.* -e https://go2docs.graylog.org.*
|
||||||
environment:
|
environment:
|
||||||
LINK_VALIDATOR_BASE_DIR: public/
|
LINK_VALIDATOR_BASE_DIR: public/
|
||||||
LINK_VALIDATOR_RETRIES: 3
|
LINK_VALIDATOR_RETRIES: 3
|
||||||
@ -127,6 +127,6 @@ depends_on:
|
|||||||
|
|
||||||
---
|
---
|
||||||
kind: signature
|
kind: signature
|
||||||
hmac: 0b9304513ddb3911087f261da41092321969b32185f4b308bae8443b08b0a380
|
hmac: 401ce37f663e531d89355639b5e42ad06fe3b3a70f211d9516a773a719e3fc7a
|
||||||
|
|
||||||
...
|
...
|
||||||
|
@ -19,7 +19,7 @@ Graylog is a centralized log management solution to capture, store and analyze l
|
|||||||
|
|
||||||
<!--more-->
|
<!--more-->
|
||||||
|
|
||||||
Fortunately, [Graylog](https://docs.graylog.org/) also knows this and recommends users to switch even if it is currently not enforced and ES 7.10 continues to work for now <!-- spellchecker-disable -->[^elastic]<!-- spellchecker-enable -->
|
Fortunately, [Graylog](https://go2docs.graylog.org) also knows this and recommends users to switch even if it is currently not enforced and ES 7.10 continues to work for now <!-- spellchecker-disable -->[^elastic]<!-- spellchecker-enable -->
|
||||||
. As you usually don't wants to operate software that no longer receives security updates, I have started to look into a migration and prepared the Container and Ansible setup. My fist mistake on this journey was to believe I can just use the latest Opensearch (OS) release. Had I read the documentation <!-- spellchecker-disable -->[^graylog]<!-- spellchecker-enable -->
|
. As you usually don't wants to operate software that no longer receives security updates, I have started to look into a migration and prepared the Container and Ansible setup. My fist mistake on this journey was to believe I can just use the latest Opensearch (OS) release. Had I read the documentation <!-- spellchecker-disable -->[^graylog]<!-- spellchecker-enable -->
|
||||||
more carefully I would have saved myself a lot of trouble...
|
more carefully I would have saved myself a lot of trouble...
|
||||||
|
|
||||||
@ -39,7 +39,7 @@ What annoys me a bit about the whole situation is the back and forth and the rat
|
|||||||
<!-- spellchecker-disable -->
|
<!-- spellchecker-disable -->
|
||||||
|
|
||||||
[^elastic]: https://www.graylog.org/post/graylog-to-add-support-for-opensearch
|
[^elastic]: https://www.graylog.org/post/graylog-to-add-support-for-opensearch
|
||||||
[^graylog]: https://docs.graylog.org/docs/migrating-to-opensearch
|
[^graylog]: https://go2docs.graylog.org/5-0/planning_your_deployment/upgrading_to_opensearch.htm
|
||||||
[^gl-github]: https://github.com/Graylog2/graylog2-server/issues/11804
|
[^gl-github]: https://github.com/Graylog2/graylog2-server/issues/11804
|
||||||
[^os-github]: https://github.com/opensearch-project/project-website/issues/661
|
[^os-github]: https://github.com/opensearch-project/project-website/issues/661
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user