Skip to content

Conversation

yelizhenden-mdb
Copy link
Collaborator

@yelizhenden-mdb yelizhenden-mdb commented Aug 19, 2025

Proposed changes

Jira ticket: CLOUDP-310539

This PR introduces automatic warning-level violation detection:

  • Runs daily as part of the metric collection job
  • Filters out warning-level violations
  • Automatically creates a Jira ticket
  • Posts a warning message with the Jira link, tagging the on-call person

Would create Jira ticket with:

Summary: Warning-level IPA violations found
Description:
Warning-level violations were found during IPA validation. Please review and add exceptions if valid, or address false positives.

Violation Summary:
• xgen-IPA-104-valid-operation-id (1 violations)

Total violations: 1

Would send Slack message:

Warning-level IPA violations found (1 violations) (@apix-platform-oncall).

Jira ticket: [DRY RUN - no ticket created]

Checklist

  • I have signed the MongoDB CLA
  • I have added tests that prove my fix is effective or that my feature works

Changes to Spectral

  • I have read the README file for Spectral Updates

Further comments

@yelizhenden-mdb yelizhenden-mdb marked this pull request as ready for review August 20, 2025 13:31
@yelizhenden-mdb yelizhenden-mdb requested review from a team as code owners August 20, 2025 13:31
fi

# Create detailed description
DESCRIPTION="Warning-level violations were found during IPA validation. Please review and add exceptions if valid, or address false positives.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Maybe we can link to the IPA wiki with the rollout process?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Added! Let me know how it sounds

Comment on lines 75 to 76
chmod +x .github/scripts/handle_warning_violations.sh
.github/scripts/handle_warning_violations.sh "$WARNING_COUNT" "$TEAM_ID" "$JIRA_API_TOKEN" "$SLACK_BEARER_TOKEN" "$SLACK_CHANNEL_ID" "$SLACK_ONCALL_USER"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Q: Do we need the chmod +x?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

We might not need it, because I will already commit the execute permission. Let me remove and try that way

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Removed

Copy link
Collaborator

@lovisaberggren lovisaberggren left a comment

Choose a reason for hiding this comment

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

LGTM, perhaps we can wait with enabling this since we currently have a lot of warning we're aware of. Could be good to enable after the current IPA projects are done

@yelizhenden-mdb
Copy link
Collaborator Author

yelizhenden-mdb commented Aug 20, 2025

@lovisaberggren I commented out the "handle warning violations step" and we can turn it on when it is ready to use. Wdyt? I don’t think filtering and creating files will add much overhead

@lovisaberggren
Copy link
Collaborator

SGTM! Can you create a ticket for enabling?

@yelizhenden-mdb yelizhenden-mdb merged commit bf9c013 into main Aug 21, 2025
12 checks passed
@yelizhenden-mdb yelizhenden-mdb deleted the CLOUDP-310539-warning-detection branch August 21, 2025 09:53
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