Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Fix] Opsgenie Analyzer Http Client #3841

Merged
merged 1 commit into from
Jan 14, 2025
Merged

[Fix] Opsgenie Analyzer Http Client #3841

merged 1 commit into from
Jan 14, 2025

Conversation

abmussani
Copy link
Contributor

Description:

Opsgenie APIs returns HTTP status code of 202 for non-safe requests. The HTTP Client for analyzer restricts response to not be in between 200 and 300. Returning error if that's happen. This PR modifies the HTTP Client for only OpsGenie Analyzer so restriction can be bypass.

Checklist:

  • Tests passing (make test-community)?
  • Lint passing (make lint this requires golangci-lint)?

@abmussani abmussani requested review from mcastorina and a team January 14, 2025 10:22
@abmussani abmussani self-assigned this Jan 14, 2025
@abmussani abmussani requested a review from a team as a code owner January 14, 2025 10:22
@abmussani
Copy link
Contributor Author

Re-ran the test-community as flaky test was failing.

@zricethezav zricethezav merged commit 9e28c7a into trufflesecurity:main Jan 14, 2025
13 checks passed
@abmussani abmussani mentioned this pull request Jan 21, 2025
Merged
2 tasks
@blsaccess blsaccess mentioned this pull request Jan 30, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ahrav ahrav ahrav approved these changes

@mcastorina mcastorina Awaiting requested review from mcastorina

Assignees

@abmussani abmussani

Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@abmussani @ahrav @zricethezav