slipway 1.0.0-alpha1

First alpha of Slipway, a Drupal front end for the Slipway deployment control plane for containerized Drupal on Kubernetes (k3s). Code moves up from dev to stage to prod, and data copies down. This module brings that workflow into Drupal's admin, gates it with Drupal permissions, and records each operation in the audit log under the Drupal user who started it.

The module does not deploy anything itself. It is a client for Slipway's HTTP API, and every operation runs in Slipway as Kubernetes Jobs.

Features

• Dashboard at /admin/slipway shows:
  • what each environment runs, and replica health
  • when data was last copied in
  • releases and snapshots
  • stalled sequences
  • the audit history
  • a live log of the running operation
• Deploy a recorded release, promote the exact image digest a lower environment runs, or deploy an image reference.
• Copy down the database and/or files, take and restore snapshots, roll back, and cancel stalled sequences.
• Permissions are separate for non-production and production. Changing production requires typing the environment name to confirm.
• Drush commands: slipway:grid, slipway:deploy, slipway:copy-down, slipway:snapshot, slipway:state.
• Status endpoint at /slipway/status, gated by a token. It reports pending updates and config drift, and Slipway can poll it in each managed environment.

Requirements

• Drupal 10.3 or 11, PHP 8.1+
• A running Slipway with HTTP API v1, which adds the API token, X-Slipway-Actor and the JSON read endpoints. Against an older Slipway, the grid and operations work, but the release, snapshot and history lists show as unavailable. The full contract is in docs/SLIPWAY_API.md.

Configuration

1. Set the base URL at Configuration » Development » Slipway. This is usually the in-cluster Service, e.g.
   http://slipway.slipway.svc.cluster.local:8080.
2. Put the secrets in settings.php, not in config. Copy-down moves the database, and config moves with it. $settings['slipway_api_token'] is required; $settings['slipway_status_token'] is optional.
3. Grant permissions. Deploy to production and Administer Slipway are restricted.

Security notes

• The API token can start any operation Slipway offers. Treat it like a deploy key.
• The module deliberately does not wrap Slipway's console endpoint, because that endpoint runs arbitrary commands.
• Access checks fail closed: if Slipway is unreachable, operation routes deny access.

Known limitations (alpha)

• Schedules are view-only. Manage them in Slipway's own UI or CLI.
• Slipway does not poll /slipway/status yet. That is planned for a later Slipway release.
• The API may still change before beta.

Changes since project creation

• Initial code commit
• Prepare 1.0.x for Drupal.org