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

[AbnormalSecurity] Expand integration commands #29994

Conversation

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

Created a new pull request as the previous one got muddled with merge conflict issues

Status

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

Related Issues

fixes: link to the issue

Description

A few sentences describing the overall goals of the pull request's commits.

Must have

  • Tests
  • Documentation

@content-bot content-bot added Contribution Thank you! Contributions are always welcome! External PR Partner Support Level Indicates that the contribution is for Partner supported pack labels Oct 2, 2023
@content-bot content-bot changed the base branch from master to contrib/wolyslager_expand-integration-commands-2 October 2, 2023 19:23
@MichaelYochpaz
Copy link
Contributor

@wolyslager Looks good. Just fix the failing validations and unit-tests.

Note that you've changed the release notes of an existing version (2_0_27.md) instead of creating a new one (and the original one of a previous version should remain untouched).

I'd recommend just reverting the changes to just revert the changes you made to the release notes file & pack_metadata.json and run demisto-sdk update-release-notes -i Packs/AbnormalSecurity -u minor.
Or you can do that manually and just copy the changed to a new file named 2_1_0.md and revert the changes on 2_0_27.md.

Also, while making the changes, pull & merge from master (if you see any conflicts to unrelated files like last time don't merge) so that we can run the build after the changes and assure it passes.

@MichaelYochpaz MichaelYochpaz added post-demo pending-contributor The PR is pending the response of its creator Partner-Approved Partner labels Oct 4, 2023
@wolyslager
Copy link
Contributor Author

@MichaelYochpaz I've fixed the failing tests and created a new release notes file (2_1_0) and reverted the changes on the previous one (2_0_27). I had to manually update the pack metadata to match 2_1_0. I also pulled an merged from master and had no conflicts 😄 - let me know if I need to do anything else! 🙏

@MichaelYochpaz MichaelYochpaz added the ready-for-instance-test In contribution PRs, this label will cause a trigger of a build with a modified pack from the PR. label Oct 4, 2023
@content-bot
Copy link
Collaborator

content-bot commented Oct 4, 2023

For the Reviewer: Successfully created a pipeline in Gitlab with url: https://code.pan.run/xsoar/content/-/pipelines/6522773

@MichaelYochpaz
Copy link
Contributor

@wolyslager There's a validation error -

[2023-10-04 14:23:07,126] [ERROR] Packs/AbnormalSecurity/ReleaseNotes/2_1_0.md: [RN111] - The 2_1_0.md release notes file contains incompatible Docker images:

  • Abnormal Security Event Collector: Release notes file has dockerimage: demisto/python3:3.10.13.74666 but the YML file has dockerimage: demisto/python3:3.10.13.75921
  • Abnormal Security: Release notes file has dockerimage: demisto/python3:3.10.13.74666 but the YML file has dockerimage: demisto/python3:3.10.13.75921
    To fix this please run: 'demisto-sdk update-release-notes -i Packs/AbnormalSecurity'

The Docker version specified in the release-notes doesn't match the one on the YAML file.
Other than that there don't seem to be any issues :)

@wolyslager
Copy link
Contributor Author

@wolyslager There's a validation error -

[2023-10-04 14:23:07,126] [ERROR] Packs/AbnormalSecurity/ReleaseNotes/2_1_0.md: [RN111] - The 2_1_0.md release notes file contains incompatible Docker images:

  • Abnormal Security Event Collector: Release notes file has dockerimage: demisto/python3:3.10.13.74666 but the YML file has dockerimage: demisto/python3:3.10.13.75921
  • Abnormal Security: Release notes file has dockerimage: demisto/python3:3.10.13.74666 but the YML file has dockerimage: demisto/python3:3.10.13.75921
    To fix this please run: 'demisto-sdk update-release-notes -i Packs/AbnormalSecurity'

The Docker version specified in the release-notes doesn't match the one on the YAML file. Other than that there don't seem to be any issues :)

Perfect! Updated it 😄 hopefully that wraps things up 🤞

@MichaelYochpaz MichaelYochpaz added ready-for-instance-test In contribution PRs, this label will cause a trigger of a build with a modified pack from the PR. Contribution Form Filled Whether contribution form filled or not. and removed ready-for-instance-test In contribution PRs, this label will cause a trigger of a build with a modified pack from the PR. labels Oct 4, 2023
Copy link
Contributor

@MichaelYochpaz MichaelYochpaz 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, good job!

@MichaelYochpaz MichaelYochpaz merged commit c590ec7 into demisto:contrib/wolyslager_expand-integration-commands-2 Oct 5, 2023
22 of 28 checks passed
MichaelYochpaz added a commit that referenced this pull request Oct 6, 2023
* AbnormalSecurity.py

* AbnormalSecurity.yml

* AbnormalSecurity_test.py

* command_examples

* README

* adding test data

* adding test files

* test file content

* test file contents

* test file contents

* test file contents

* test file contents

* test file

* test file content

* release notes

* Secrets

* updating version

* updating docker image

* adjusting abuse mailbox context path

* adding test files

* adding test data

* adding test files

* fixing tests

* test data

* nit - tests

* nit -tests

* nit - remove hardcoded last fetch time

* remove page numbers from threats command

* remove nextPageNumber key

* remove hardcoded last fetch time

* linting fix

* markdown fixes

* release notes

* fix vendors list command

* fix vendor cases command

* tests fix

* nit - linting error:

* update version

* fixing context output

* dont include vendors key

* exclude vendors key

* nit

* exlude vendorCases key

* nit

* removing white spacE

* fix unit tests

* revert pack metadata change

* revert release notes change

* nit

* revert release notes

* nit

* new release notes file

* nit

* update pack metadata

* fix docker version in release files

Co-authored-by: William Olyslager <wolyslager@abnormalsecurity.com>
Co-authored-by: Michael Yochpaz <8832013+MichaelYochpaz@users.noreply.github.com>
sapirshuker pushed a commit that referenced this pull request Dec 21, 2023
* AbnormalSecurity.py

* AbnormalSecurity.yml

* AbnormalSecurity_test.py

* command_examples

* README

* adding test data

* adding test files

* test file content

* test file contents

* test file contents

* test file contents

* test file contents

* test file

* test file content

* release notes

* Secrets

* updating version

* updating docker image

* adjusting abuse mailbox context path

* adding test files

* adding test data

* adding test files

* fixing tests

* test data

* nit - tests

* nit -tests

* nit - remove hardcoded last fetch time

* remove page numbers from threats command

* remove nextPageNumber key

* remove hardcoded last fetch time

* linting fix

* markdown fixes

* release notes

* fix vendors list command

* fix vendor cases command

* tests fix

* nit - linting error:

* update version

* fixing context output

* dont include vendors key

* exclude vendors key

* nit

* exlude vendorCases key

* nit

* removing white spacE

* fix unit tests

* revert pack metadata change

* revert release notes change

* nit

* revert release notes

* nit

* new release notes file

* nit

* update pack metadata

* fix docker version in release files

Co-authored-by: William Olyslager <wolyslager@abnormalsecurity.com>
Co-authored-by: Michael Yochpaz <8832013+MichaelYochpaz@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Contribution Form Filled Whether contribution form filled or not. Contribution Thank you! Contributions are always welcome! External PR Partner Support Level Indicates that the contribution is for Partner supported pack Partner Partner-Approved pending-contributor The PR is pending the response of its creator post-demo ready-for-instance-test In contribution PRs, this label will cause a trigger of a build with a modified pack from the PR.
Projects
None yet
4 participants