Add requireAllDemandsAndIgnoreOthers flag#5839
Conversation
|
Semgrep found 1 Consider to use well-defined context Ignore this finding from context-todo.Semgrep found 1 Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'. Ignore this finding from no-direct-write-to-responsewriter. |
|
Semgrep found 1 Consider to use well-defined context Ignore this finding from context-todo.Semgrep found 1 Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'. Ignore this finding from no-direct-write-to-responsewriter. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
|
This issue has been automatically closed due to inactivity. |
|
/run-e2e pipeline |
|
Semgrep found 1 Consider to use well-defined context Ignore this finding from context-todo.Semgrep found 1 Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'. Ignore this finding from no-direct-write-to-responsewriter. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
|
Semgrep found 1 Consider to use well-defined context Ignore this finding from context-todo.Semgrep found 1 Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'. Ignore this finding from no-direct-write-to-responsewriter. |
|
Semgrep found 1 Consider to use well-defined context Ignore this finding from context-todo Semgrep found 1 Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'. |
zroubalik
left a comment
There was a problem hiding this comment.
Could you please fix DCO and add ingore for semgrep for the test?
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
|
Semgrep found 1 Consider to use well-defined context Ignore this finding from context-todo Semgrep found 1 Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'. |
|
I've fixed DCO and moved the documentation kedacore/keda-docs#1496 to 2.17 |
jan-mrm
left a comment
There was a problem hiding this comment.
About the 'Semgrep' I'd think they want something like those 2 suggestions that I just made here - a comment to ignore the 2 findings
|
Semgrep found 1 Consider to use well-defined context Ignore this finding from context-todo Semgrep found 1 Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'. |
|
/run-e2e azure |
|
/run-e2e azure |
|
/run-e2e azure |
|
Could you fix DCO please? https://github.com/kedacore/keda/pull/5839/checks?check_run_id=36986822520 I merged the docs by mistake and this PR is left :/ |
Signed-off-by: jonas <jonas.rudlang@gmail.com>
|
/run-e2e azure |
Signed-off-by: mittalvaibhav1 <mittalvaibhavandroid@gmail.com>
This PR adds an extra option
requireAllDemandsAndIgnoreOthers(name tbd) to the azure pipeline scaler which ensures that all demands in the scaler definition is present in the incoming job, while ignoring any other demands the job may have.This is different from
requireAllDemandswhich requires all demands to be an exact match.Checklist
Document the azure pipeline property requireAllDemandsAndIgnoreOthers keda-docs#1496
Fixes #5579