Remove JIRA_SCHEMA_ID from entire application

- Remove JIRA_SCHEMA_ID from all documentation, config files, and scripts
- Update generate-schema.ts to always auto-discover schemas dynamically
- Runtime application already discovers schemas via /objectschema/list API
- Build script now automatically selects schema with most objects
- Remove JIRA_SCHEMA_ID from docker-compose.yml, Azure setup scripts, and all docs
- Application is now fully schema-agnostic and discovers schemas automatically
This commit is contained in:
2026-01-22 22:56:29 +01:00
parent f4399a8e4e
commit 57e4adc69c
14 changed files with 63 additions and 47 deletions

View File

@@ -134,7 +134,6 @@ The following environment variables have been **REMOVED** from the codebase and
- `SESSION_SECRET`: Should be a secure random string in production (generate with `openssl rand -base64 32`)
- `ENCRYPTION_KEY`: Must be exactly 32 bytes when base64 decoded (generate with `openssl rand -base64 32`)
- `JIRA_SCHEMA_ID`: Required for Jira Assets integration
### Application Branding