Skip to content

Fix k8s_version_policy.py to log on stderr (instead of stdout) - #1208

Merged
mbuechse merged 1 commit into
mainfrom
fix/scs-210-test-output
Jun 16, 2026
Merged

Fix k8s_version_policy.py to log on stderr (instead of stdout)#1208
mbuechse merged 1 commit into
mainfrom
fix/scs-210-test-output

Conversation

@mbuechse

Copy link
Copy Markdown
Contributor

No description provided.

@mbuechse

Copy link
Copy Markdown
Contributor Author

Result of version policy check cannot be seen on
https://compliance.sovereignit.cloud/page/report/62965e1f-87d2-4228-988e-0d2d6b42a127#version-policy-check
because it erroneously gets logged on stdout.

(This will change once again with #1073 or so, but for now, this fix is good.)

@depressiveRobot depressiveRobot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Really a small change, so this is fine.

However, I still don't quite understand it. Do you mean that in the redacted state, the reason why the test fails cannot be seen?

@mbuechse

Copy link
Copy Markdown
Contributor Author

Yes, in the redacted state, only lines starting with ERROR or WARNING on stderr are shown. Also, no one would expect them in stdout, even if they were shown.

Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
@mbuechse
mbuechse force-pushed the fix/scs-210-test-output branch from c8b8041 to b04ccf5 Compare June 16, 2026 14:06
@mbuechse
mbuechse merged commit 888073b into main Jun 16, 2026
7 checks passed
@mbuechse
mbuechse deleted the fix/scs-210-test-output branch June 16, 2026 14:06
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.

2 participants