FOUR-31727: Fix DevLink bundle listing and selector search

[eiresendez]

Issue & Reproduction Steps

FOUR-31727 fixes an issue where DevLink bundles outside the first API page were not available from the UI. To reproduce, create more than 15 local bundles, then go to /admin/devlink/local-bundles or open an Add to Bundle modal from a supported asset list. The admin route only displayed the first page of bundles, and the dropdown search could not find bundles that were not already loaded client-side.

Solution

• Added pagination to the local DevLink bundles admin list.
• Updated the local bundles admin list to request newest bundles first.
• Updated the Add to Bundle dropdown to load the latest 100 editable bundles.
• Added backend search support to the shared backend select used by Add to Bundle.
• Added API coverage for local bundle pagination, filtering, editable filtering, and explicit newest-first ordering.

How to Test

Automated test run:
vendor/bin/phpunit tests/Feature/Api/DevLinkTest.php --filter LocalBundles

Manual verification:

1. Create more than 100 local editable bundles.
2. Open /admin/devlink/local-bundles and confirm bundles are paginated and newest bundles appear first.
3. Open an Add to Bundle modal and confirm the newest 100 editable bundles are available.
4. Search for an older bundle in the dropdown and confirm it is found through backend search.

Related Tickets & Packages

• https://processmaker.atlassian.net/browse/FOUR-31727

ci:deploy

.

[Kookster310]

QA server K8S was successfully deployed https://ci-2ba51b845d.engk8s.processmaker.net

[CarliPinell]

Thanks for the fix — pagination, newest-first ordering, and remote search address the reported DevLink bundle listing issue well, and the new API tests give good coverage.

I left two inline notes on BackendSelect.vue around remote-search UX and request ordering. Neither is a merge blocker from my side.

[CarliPinell]

Minor observations. Approved.

[vladyrichter]

QA server K8S was successfully deployed https://ci-2ba51b845d.engk8s.processmaker.net

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
34069781	Triggered	Generic Password	8b915fa	resources/views/auth/passwords/reset.blade.php	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[eiresendez]

Please disregard the GitGuardian warning, as it is a false positive inherited from develop through the latest merge. The same finding was previously reported in PR #8871 under GitGuardian incident 34069781.

[vladyrichter]

QA server K8S was successfully deployed https://ci-2ba51b845d.engk8s.processmaker.net