Appearance
Environments
- Frontend:
src/routes/private/environments/· Backend:Features/Environments/
Overview
Environments are deployment tiers (e.g. dev, test, prod). Tenants belong to an environment, and many admin resources (peripherals, notifications, connection strings) are scoped per environment. The Environments page also exposes diagnostic actions for the environment's data store and file store.
GraphQL operations
| Operation | Purpose |
|---|---|
createEnvironment / updateEnvironment / deleteEnvironment | Environment CRUD |
notices(environmentId) | Notices for an environment |
saveNotification / clearNotification | Manage a notice |
environmentPermissions(environmentId) | Permissions available in an environment |
testDataConnection(type, connectionString) | Test a data-store (SQL) connection |
testFileConnection(type, connectionString) | Test a file-store (storage) connection |
getUserEmailsUrl | CSV download URL for tenant user emails (Keycloak auth DB) |
Notices
Notices are per-environment messages shown to users of that environment (editable via the editor.svelte — message + start/end date).
REST
Features/Environments/EnvironmentsController.cs— downloads the tenant user email listing as CSV.
Related
- Tenants — tenants are scoped to environments.
- Peripherals — peripheral data is per-environment.