Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Ad Poller Bundle Laravel Package

gtt/ad-poller-bundle

GTT Ad Poller Bundle is a Symfony bundle for scheduled Active Directory polling. It runs configurable LDAP queries and provides hooks to import or synchronize users and groups, helping keep local identity data current and integrate AD-backed accounts into your application.

View on GitHub
Deep Wiki
Context7

Getting Started

  • Treat 1.1.0 as a dependency migration release: the package now requires laminas/* instead of zendframework/*.
  • Upgrade with composer update <package> --with-dependencies, then inspect composer.lock for lingering zendframework/* entries.
  • Look first at the package service provider, published config, README examples, public contracts/facades, and any PSR-7/HTTP integration points.
  • First use case: resolve the package’s main service from Laravel’s container in a controller, job, or command, then add a smoke test covering the same path used in production.

Implementation Patterns

  • Keep package usage behind a thin app-level service/action so future dependency changes do not leak across controllers and jobs.
  • Prefer constructor injection/container resolution over facades; bind package interfaces in a service provider when available.
  • Keep package config in config/*.php and environment-specific values in .env; validate with php artisan config:cache during deployment.
  • In tests, bind fakes or use the package’s test helpers; run CI against both normal and --prefer-lowest dependency sets.
  • Use composer why laminas/* and composer why zendframework/* to understand dependency graph changes before adjusting constraints.

Gotchas and Tips

  • The main 1.1.0 risk is transitive dependency conflict: apps or other packages still pinned to zendframework/* may not resolve cleanly with laminas/* equivalents.
  • If you extended package internals that imported Zend\... namespaces, update imports to Laminas\... or avoid relying on internals.
  • Avoid keeping both Zend and Laminas versions of the same component; duplicate PSR implementations can cause confusing DI/type errors.
  • After upgrading, run composer dump-autoload, php artisan config:clear, php artisan cache:clear, and feature tests.
  • Check Laravel/PHP version constraints in composer.json; dependency-only releases can still change minimum versions indirectly.
  • Extension points are likely unchanged: service provider bindings, config, middleware/commands, and PSR factories. Confirm against the README before adopting.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
se7enxweb/flysystem
lampwick/laravel
jeslage/statamic-emojis
micahdshackelford/rmap-laravel
draftsmaninc/draftsman
square-bit/laravel-volition
himito/laravel-mailman
htinlynn/genius-helper
maco-studios/hephaestus
elmogy/larafast
xeviant/laravel-paystack
gorilladash/laravel-website-sdk
martialbe/flysystem-oss
chondal/3312client
jeroen-g/flickr
opscale-co/nova-genbi
itsjustvita/laravel-retention
tequilarapido/trackit
gregsphotography/site-builder-filament
cabaoctavio/laravel-query-log