Write log entry when Azure DevOps API Rate Limit is (nearly) reached

[raherrebrugh]

Azure Pipelines Scalar

• Write log entry when Azure DevOps API Rate Limit is (nearly) reached

Checklist

• When introducing a new scaler, I agree with the scaling governance policy
• I have verified that my change is according to the deprecations & breaking changes policy
• Tests have been added
• Changelog has been updated and is aligned with our changelog requirements
• A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
• A PR is opened to update the documentation on (repo) (if applicable)
• Commits are signed with Developer Certificate of Origin (DCO - learn more)

Fixes #6284

Not related to other PRs

[semgrep-app]

Semgrep found 1 context-todo finding:

• pkg/scalers/azure_pipelines_scaler_test.go
  • L304 - Triage

Consider to use well-defined context

_{Ignore this finding from context-todo.}

Semgrep found 1 no-direct-write-to-responsewriter finding:

• pkg/scalers/azure_pipelines_scaler_test.go
  • L343 - Triage

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.}

[raherrebrugh]

Semgrep found 1 context-todo finding:

• pkg/scalers/azure_pipelines_scaler_test.go

  • L304 - Triage

Consider to use well-defined context

Ignore this finding from context-todo.
Semgrep found 1 no-direct-write-to-responsewriter finding:

• pkg/scalers/azure_pipelines_scaler_test.go

  • L343 - Triage

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.

I haven't changed this code, how should I go about resolving these semgrep issues?

[JorTurFer]

Nice improvement! Thanks 🙇

[JorTurFer]

Semgrep found 1 context-todo finding:

• pkg/scalers/azure_pipelines_scaler_test.go

  • L304 - Triage

Consider to use well-defined context
Ignore this finding from context-todo.
Semgrep found 1 no-direct-write-to-responsewriter finding:

• pkg/scalers/azure_pipelines_scaler_test.go

  • L343 - Triage

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.

I haven't changed this code, how should I go about resolving these semgrep issues?

Don't worry, I've ignored those findings for the PR and the check should pass now

[JorTurFer]

/run-e2e pipeline
Update: You can check the progress here