ring:dev-multi-tenant

The workflow orchestrates multi-tenant development by auto-detecting stacks like PostgreSQL, MongoDB, Redis, RabbitMQ, and S3. It identifies whether your service is a plugin or product, then dispatches gate-based tasks to enforce tenant isolation and per-tenant authentication.

Yes, you can use this orchestrator with MongoDB and Redis stacks. It automatically detects these technologies during the multi-tenant development process and applies the appropriate infrastructure changes and compliance gates for your service type.

JWT tenantId authentication for plugin services works by enforcing per-tenant isolation through gate-based tasks and M2M secret management. The orchestrator uses lib-auth v2 and Secrets Manager to handle authentication and enforce canonical Ring standards for plugins.

Gate-based tenant isolation in multi-tenant Golang applications is a workflow pipeline that enforces compliance, infrastructure changes, and per-tenant authentication. It executes via backend-engineer-golang gates to ensure services meet canonical Ring standards during migration.

Yes, you need lib-commons v4 to implement per-tenant tenant-manager patterns. The orchestrator loads these patterns via WebFetch and uses lib-commons v4 alongside lib-auth v2 as dependencies to enforce per-tenant authentication and isolation.