Skip to content

Conversation

@oakrizan
Copy link
Contributor

What is the problem this PR solves?

// Please do not just reference an issue. Explain WHAT the problem this PR solves here.

How does this PR solve the problem?

// Explain HOW you solved the problem in your code. It is possible that during PR reviews this changes and then this section should be updated.

How to test this PR locally

Design Checklist

  • I have ensured my design is stateless and will work when multiple fleet-server instances are behind a load balancer.
  • I have or intend to scale test my changes, ensuring it will work reliably with 100K+ agents connected.
  • I have included fail safe mechanisms to limit the load on fleet-server: rate limiting, circuit breakers, caching, load shedding, etc.

Checklist

  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in ./changelog/fragments using the changelog tool

Related issues

@prodsecmachine
Copy link

prodsecmachine commented Aug 14, 2025

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

license/snyk check is complete. No issues have been found. (View Details)

@mergify
Copy link
Contributor

mergify bot commented Aug 14, 2025

This pull request does not have a backport label. Could you fix it @oakrizan? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-./d./d is the label to automatically backport to the 8./d branch. /d is the digit
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

@oakrizan oakrizan force-pushed the feature/e2e-tests-on-macos branch 5 times, most recently from 5939366 to 310bc92 Compare August 15, 2025 07:56
@mergify
Copy link
Contributor

mergify bot commented Aug 15, 2025

This pull request is now in conflicts. Could you fix it @oakrizan? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b feature/e2e-tests-on-macos upstream/feature/e2e-tests-on-macos
git merge upstream/main
git push upstream feature/e2e-tests-on-macos

@oakrizan oakrizan force-pushed the feature/e2e-tests-on-macos branch from 310bc92 to f61c84b Compare August 15, 2025 08:06
@elastic-sonarqube
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@oakrizan oakrizan force-pushed the feature/e2e-tests-on-macos branch 10 times, most recently from 76916b6 to 1aad174 Compare August 20, 2025 12:17
@mergify
Copy link
Contributor

mergify bot commented Aug 20, 2025

This pull request is now in conflicts. Could you fix it @oakrizan? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b feature/e2e-tests-on-macos upstream/feature/e2e-tests-on-macos
git merge upstream/main
git push upstream feature/e2e-tests-on-macos

@oakrizan oakrizan force-pushed the feature/e2e-tests-on-macos branch 9 times, most recently from c707aac to 0b96184 Compare August 22, 2025 13:23
@oakrizan oakrizan force-pushed the feature/e2e-tests-on-macos branch 20 times, most recently from bfcfbc6 to 35931dd Compare September 3, 2025 16:13
@oakrizan oakrizan force-pushed the feature/e2e-tests-on-macos branch from 35931dd to 709b2e9 Compare September 3, 2025 16:16
@oakrizan oakrizan force-pushed the feature/e2e-tests-on-macos branch 3 times, most recently from 0739784 to deaa262 Compare September 4, 2025 09:41
@oakrizan oakrizan force-pushed the feature/e2e-tests-on-macos branch from deaa262 to 41dcead Compare September 4, 2025 10:03
@mergify
Copy link
Contributor

mergify bot commented Sep 5, 2025

This pull request is now in conflicts. Could you fix it @oakrizan? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b feature/e2e-tests-on-macos upstream/feature/e2e-tests-on-macos
git merge upstream/main
git push upstream feature/e2e-tests-on-macos

@oakrizan oakrizan closed this by deleting the head repository Oct 28, 2025
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