feat: Trigger Lagoon Deployments for App Instances

[dan2k3k4]

Introduces the ability to trigger Lagoon deployments for Polydock App Instances directly from the Polydock Engine.

Adds two new Artisan commands for bulk or single-instance deployments and integrates a "Trigger Deploy" action into the Filament Admin UI.

Key Changes

1. New Console Commands
   • polydock:instances:run-lagoon-command:
     • Method: Uses the Lagoon GraphQL API (via FreedomtechHosting\FtLagoonPhp\Client).
     • Features:
       • Supports concurrency (default: 1) for faster bulk operations.
       • Interactive mode allows selecting specific instances from a list (unless --force is used).
       • Handles authentication via SSH key exchange for Lagoon tokens.
   • polydock:instances:trigger-deploy:
     • Method: Wrapper around the system's lagoon CLI tool.
     • Features: Simple execution of lagoon deploy -p [project] -e [branch] for running instances.
2. Admin UI Updates
   • ViewPolydockAppInstance:
     • Added a Trigger Deploy header action.
     • Displays a modal confirming the branch and showing the "Last Deployment Date".
     • Executes the deployment via the local lagoon CLI.
3. Model Updates
   • PolydockAppInstance: Added getName() and setName() convenience methods.
   4. Testing
   • Added tests/Feature/Console/Commands/RunLagoonCommandOnAppInstancesTest.php covering:
     • Serial vs. Concurrent execution.
     • Variable-only deployments.
     • Error handling for missing metadata.
     • Interactive prompts.

How to Test

CLI (API-based):

# Dry run / Interactive selection
php artisan polydock:instances:run-lagoon-command {app_uuid}

# Force run on all instances concurrently
php artisan polydock:instances:run-lagoon-command {app_uuid} --force --concurrency=5

CLI (Lagoon CLI-based):
php artisan polydock:instances:trigger-deploy {app_uuid}

Admin UI:

1. Navigate to a Polydock App Instance view page.
2. Click the new Trigger Deploy button in the header.
3. Confirm the action in the modal.

[Copilot]

Pull request overview

Adds Lagoon deployment/command triggering capabilities for Polydock App Instances from both Artisan commands and the Filament Admin UI, leveraging the freedomtech-hosting/ft-lagoon-php GraphQL client and SSH-based token retrieval.

Changes:

• Introduces new Lagoon-related Artisan commands for bulk/single-instance deploy triggers and for running allowed commands across instances (with optional concurrency).
• Adds a Filament “Trigger Deploy” header action (with last deployment lookup) on the App Instance view page.
• Updates Lagoon/Amazee AI related dependencies and enhances Lagoon token initialization diagnostics.

Reviewed changes

Copilot reviewed 12 out of 13 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
tests/Feature/Filament/CreatePolydockAppInstanceTest.php	Import ordering tweak.
tests/Feature/Console/Commands/RunLagoonCommandOnAppInstancesTest.php	Adds feature tests for the new command execution workflow.
config/polydock.php	Changes Amazee AI backend provider debug default.
composer.json	Bumps Lagoon/Polydock-related package versions.
composer.lock	Locks updated dependency graph (incl. new packages).
app/Services/LagoonClientService.php	Centralizes Lagoon client config + SSH token retrieval + GraphQL initialization.
app/PolydockServiceProviders/PolydockServiceProviderFTLagoon.php	Improves token caching/error diagnostics; throws on missing token.
app/PolydockEngine/Engine.php	Adjusts required-variable validation and backfills Lagoon runtime defaults on legacy instances.
app/Filament/Admin/Resources/UserRemoteRegistrationResource.php	Removes unused import.
app/Filament/Admin/Resources/PolydockAppInstanceResource/Pages/ViewPolydockAppInstance.php	Adds “Trigger Deploy” action + last deployment display via Lagoon API.
app/Console/Commands/TriggerLagoonDeployOnAppInstances.php	New bulk deploy-trigger command (API-based, optional concurrency).
app/Console/Commands/TriggerLagoonDeployOnAppInstance.php	New single-instance deploy-trigger command (API-based).
app/Console/Commands/RunLagoonCommandOnAppInstances.php	New bulk command-runner via Lagoon API with allowlist + optional concurrency.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

LagoonClientService::getLagoonToken() invokes the bound polydock.lagoon.token_fetcher callable with the $config array, but the test binds a zero-arg closure. This will throw an ArgumentCountError when the command runs. Bind a callable that accepts the config parameter (e.g., fn (array $config) => 'fake-token') or change the service to support zero-arg fetchers.

[dan2k3k4]

@copilot open a new pull request to apply changes based on this feedback

[Copilot]

Concurrent mode builds a child-process command for polydock:instances:run-lagoon-command but omits the required command_name argument and points at the wrong command entirely for deployments. As written, the spawned processes will fail to start (and no deploy will be triggered). Consider adding an --instance-id worker mode to this command and have the pool call polydock:instances:trigger-deploy (or call polydock:app-instance:trigger-deploy per instance) with the correct args/options instead of run-lagoon-command.

[Copilot]

@dan2k3k4 I've opened a new pull request, #96, to work on those changes. Once the pull request is ready, I'll request review from you.

[Copilot]

@dan2k3k4 I've opened a new pull request, #97, to work on those changes. Once the pull request is ready, I'll request review from you.