Update elasticsearch Docker tag to v7.17.10

[renovate]

This PR contains the following updates:

Package	Update	Change
elasticsearch	patch	7.17.4 -> 7.17.10

---

Release Notes

elastic/elasticsearch

v7.17.10: Elasticsearch 7.17.10

Compare Source

Downloads: https://elastic.co/downloads/elasticsearch
Release notes: https://www.elastic.co/guide/en/elasticsearch/reference/7.17/release-notes-7.17.10.html

v7.17.9: Elasticsearch 7.17.9

Compare Source

Downloads: https://elastic.co/downloads/elasticsearch
Release notes: https://www.elastic.co/guide/en/elasticsearch/reference/7.17/release-notes-7.17.9.html

v7.17.8: Elasticsearch 7.17.8

Compare Source

Downloads: https://elastic.co/downloads/elasticsearch
Release notes: https://www.elastic.co/guide/en/elasticsearch/reference/7.17/release-notes-7.17.8.html

v7.17.7: Elasticsearch 7.17.7

Compare Source

Downloads: https://elastic.co/downloads/elasticsearch
Release notes: https://www.elastic.co/guide/en/elasticsearch/reference/7.17/release-notes-7.17.7.html

v7.17.6: Elasticsearch 7.17.6

Compare Source

Downloads: https://elastic.co/downloads/elasticsearch
Release notes: https://www.elastic.co/guide/en/elasticsearch/reference/7.17/release-notes-7.17.6.html

v7.17.5: Elasticsearch 7.17.5

Compare Source

Downloads: https://elastic.co/downloads/elasticsearch
Release notes: https://www.elastic.co/guide/en/elasticsearch/reference/7.17/release-notes-7.17.5.html

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	Secret	Commit	Filename
5530654	AWS Keys	8b6d8ef	infrastucture/uploader/uploader_test.go	View secret
5530653	DigitalOcean Spaces Keys	f8e4607	infrastucture/uploader/uploader_test.go	View secret
5530653	DigitalOcean Spaces Keys	1445d8f	infrastucture/uploader/uploader_test.go	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.