Skip to content

[Backport 2025.2] feature(LogCollector): Use argus proxy URLs instead of S3 links #11253

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

Merged
merged 1 commit into from
Jul 1, 2025

Conversation

scylladbbot
Copy link

This change changes how links to the logs and screenshots are displayed
to the user in SCT reporting - instead of using raw S3 urls with public
bucket, the provided link now proxies the result through argus, allowing
bucket to be private.

Task: scylladb/qa-tasks#1874

Testing

PR pre-checks (self review)

  • I added the relevant backport labels
  • I didn't leave commented-out/debugging code

Reminders

  • Add New configuration option and document them (in sdcm/sct_config.py)

  • Add unit tests to cover my changes (under unit-test/ folder)

  • Update the Readme/doc folder relevant to this change (if needed)

  • (cherry picked from commit 218e600)

Parent PR: #11229

This change changes how links to the logs and screenshots are displayed
to the user in SCT reporting - instead of using raw S3 urls with public
bucket, the provided link now proxies the result through argus, allowing
bucket to be private.

Closes scyllab/qa-tasks#1874

(cherry picked from commit 218e600)
@fruch fruch merged commit d26a6b3 into scylladb:branch-2025.2 Jul 1, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants