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.

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

[XDR - IR] revert #35932 #36580

Merged
merged 4 commits into from
Oct 2, 2024
Merged

[XDR - IR] revert #35932 #36580

merged 4 commits into from
Oct 2, 2024

Conversation

jlevypaloalto
Copy link
Contributor

Contributing to Cortex XSOAR Content

Make sure to register your contribution by filling the contribution registration form

The Pull Request will be reviewed only after the contribution registration form is filled.

Status

  • In Progress
  • Ready
  • In Hold - (Reason for hold)

Related Issues

fixes:

  1. XSUP-39965
  2. XSUP-41879
  3. XSUP-41984
  4. XSUP-42134

Description

Revert version 6.1.73 in #35932.

Must have

  • Tests
  • Documentation

Copy link

github-actions bot commented Oct 1, 2024

Coverage

Coverage Report
FileStmtsMissCoverMissing
Packs/CortexXDR/Integrations/CortexXDRIR
   CortexXDRIR.py6498786%61, 69, 73–75, 146–147, 208–212, 214, 217, 220, 224, 250–254, 256, 263–266, 277, 280, 283, 289, 292, 318, 323, 331, 333, 336–340, 342, 425–430, 479, 517, 532–533, 550, 560, 620, 623, 650, 657, 659, 736–737, 739, 792, 981–983, 986, 989, 994, 1029, 1037, 1060, 1088–1089, 1140, 1149, 1151–1153, 1156, 1159–1160, 1197–1200, 1232, 1249
TOTAL6498786% 

Tests Skipped Failures Errors Time
328 0 💤 0 ❌ 0 🔥 17.099s ⏱️

Copy link
Contributor

@YuvHayun YuvHayun left a comment

Choose a reason for hiding this comment

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

Looks good.
approved for my side.
Just note the comments about the RN.
Make sure @JudahSchwartz also review it.


##### Palo Alto Networks Cortex XDR - Investigation and Response

- Reverting the de-duplication mechanism added in version `6.1.73`.
Copy link
Contributor

Choose a reason for hiding this comment

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

This RN should be "fixed an issue where - {the issue}"
Additionally, add a note inside 6.1.73 RN that the version is invalid (like the example I sent on slack)

@@ -70,52 +70,6 @@
},
{
"incident_id": "4",
"creation_time": 100000001,
"modification_time": 1575813875168,
Copy link
Contributor

Choose a reason for hiding this comment

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

Is it really necessary to revert here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

it will make it easier for me to unrevert

@jlevypaloalto jlevypaloalto merged commit ee07922 into master Oct 2, 2024
16 checks passed
@jlevypaloalto jlevypaloalto deleted the jl-XDR-revert branch October 2, 2024 13:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants