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

Update codeowners as per 2024 Security Integrations Team reorganization #37696

Merged
merged 2 commits into from
Jan 25, 2024
Merged

Update codeowners as per 2024 Security Integrations Team reorganization #37696

merged 2 commits into from
Jan 25, 2024

Conversation

norrietaylor
Copy link
Member

@norrietaylor norrietaylor commented Jan 22, 2024 •
edited
Loading

This PR updates the CODEOWNERS file per the 2024 Security Integrations Team reorganization.

Note: There are some warnings for the change that will be resolved once we grant @elastic/sec-deployment-and-devices and @elastic/sec-windows-platform write access to the beats repository.

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jan 22, 2024
@norrietaylor norrietaylor force-pushed the norrietaylor/sitreorg-codeowners branch from fed508c to 5e006f7 Compare January 22, 2024 17:15
@mergify Mergify
Copy link
Contributor

mergify bot commented Jan 22, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @norrietaylor? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Duration: 13 min 32 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@norrietaylor norrietaylor force-pushed the norrietaylor/sitreorg-codeowners branch from 5e006f7 to 05a089a Compare January 22, 2024 21:29
@norrietaylor norrietaylor added Team:Security-Linux Platform Linux Platform Team in Security Solution Team:Security-Service Integrations Security Service Integrations Team labels Jan 22, 2024
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jan 22, 2024
@norrietaylor norrietaylor added Team:Security-Integrations Team:Security-Windows Platform Windows Platform Team in Security Solution Team:Security-Deployment and Devices Deployment and Devices Team in Security Solution Team:Security-Edge Integrations Security Edge Integrations Team labels Jan 22, 2024
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2024-01-22T21:29:54.117+0000

  • Duration: 13 min 34 sec

Test stats 🧪

Test Results
Failed 0
Passed 3
Skipped 0
Total 3

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@norrietaylor norrietaylor force-pushed the norrietaylor/sitreorg-codeowners branch from 05a089a to 608ad29 Compare January 22, 2024 21:46
@norrietaylor norrietaylor marked this pull request as ready for review January 22, 2024 21:54
@norrietaylor norrietaylor requested a review from a team as a code owner January 22, 2024 21:54
@norrietaylor norrietaylor requested review from belimawr and faec January 22, 2024 21:54
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2024-01-22T21:46:34.962+0000

  • Duration: 13 min 24 sec

Test stats 🧪

Test Results
Failed 0
Passed 3
Skipped 0
Total 3

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@pierrehilbert
Copy link
Collaborator

I just did the necessary on the repository and approved the PR.
Thanks.

@norrietaylor norrietaylor force-pushed the norrietaylor/sitreorg-codeowners branch from 608ad29 to de8d508 Compare January 25, 2024 14:51
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Duration: 13 min 32 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Duration: 12 min 19 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@norrietaylor norrietaylor merged commit e9d8572 into main Jan 25, 2024
20 checks passed
@norrietaylor norrietaylor deleted the norrietaylor/sitreorg-codeowners branch January 25, 2024 19:16
Scholar-Li pushed a commit to Scholar-Li/beats that referenced this pull request Feb 5, 2024
@norrietaylor @pierrehilbert @Scholar-Li
Update codeowners as per 2024 Security Integrations Team reorganizati…
8925bbb 
…on (elastic#37696)

Co-authored-by: Pierre HILBERT <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@nfritts nfritts nfritts approved these changes

@ebeahan ebeahan ebeahan approved these changes

@pierrehilbert pierrehilbert pierrehilbert approved these changes

@belimawr belimawr belimawr approved these changes

@epixa epixa Awaiting requested review from epixa

@narph narph Awaiting requested review from narph

@faec faec Awaiting requested review from faec faec was automatically assigned from elastic/elastic-agent-data-plane

Assignees

@norrietaylor norrietaylor

Labels
Team:Security-Deployment and Devices Deployment and Devices Team in Security Solution Team:Security-Edge Integrations Security Edge Integrations Team Team:Security-Linux Platform Linux Platform Team in Security Solution Team:Security-Service Integrations Security Service Integrations Team Team:Security-Windows Platform Windows Platform Team in Security Solution
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
6 participants
@norrietaylor @elasticmachine @pierrehilbert @belimawr @ebeahan @nfritts