-
Notifications
You must be signed in to change notification settings - Fork 40
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
fix(config): update vomsproxy fallback image #475
Conversation
Make sure the secret key is propagated to the Flask app, instead of incorrectly using the default one.
Configure the security context of Kubernetes jobs to disallow privilege escalation.
Configure the security context of Kubernetes jobs to disallow privilege escalation.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #475 +/- ##
=======================================
Coverage 48.07% 48.07%
=======================================
Files 17 17
Lines 1302 1302
=======================================
Hits 626 626
Misses 676 676
|
@@ -66,7 +66,7 @@ | |||
|
|||
|
|||
VOMSPROXY_CONTAINER_IMAGE = os.getenv( | |||
"VOMSPROXY_CONTAINER_IMAGE", "docker.io/reanahub/reana-auth-vomsproxy:1.2.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestion: This PR is not really needed, since upgrade to 1.3.0 is already done on the maint-0.9
branch, and will come to the master
branch during maint-to-master upstream merge. Let's rather do that, since it'll bring PUNCH backend support etc.
Duplicate of #466. |
No description provided.