# Which Problems Are Solved Login integration tests are not executed in the pipeline # How the Problems Are Solved The login integration tests are fixed and added as a pipeline workflow. It tests against the built login docker image. On pipeline failures, developers are guided on how to fix them using a dev container configured for this purpose. # Additional Changes - email domains are replaced by example.com. In case the tests were accidentally run against a cloud instance, it wouldn't cause bounces. - pnpm is upgraded, because the --filter argument doesn't work for the install command on the old version. - The login Dockerfile is optimized for docker image builds # Additional Changes From Review for https://github.com/zitadel/zitadel/pull/10305 These changes were requested from @peintnermax - The base dev container starts without any services besides the database and the dev container itself - CONTRIBUTING.md is restructured - To reproduce pipeline checks, only the devcontainer CLI and Docker are needed. This is described in the CONTRIBUTING.md - The convenience npm script "generate" is added # Additional Context - Follow-up for PR https://github.com/zitadel/zitadel/pull/10305 - Base for https://github.com/zitadel/zitadel/issues/10277
Console Angular App
This is the ZITADEL Console Angular application.
Development
Prerequisites
- Node.js 18 or later
- pnpm (latest)
Installation
pnpm install
Proto Generation
The Console app uses dual proto generation with Turbo dependency management:
@zitadel/protogeneration: Modern ES modules with@bufbuild/protobuffor v2 APIs- Local
buf.gen.yamlgeneration: Traditional protobuf JavaScript classes for v1 APIs
The Console app's turbo.json ensures that @zitadel/proto#generate runs before the Console's own generation, providing both:
- Modern schemas from
@zitadel/proto(e.g.,UserSchema,DetailsSchema) - Legacy classes from
src/app/proto/generated(e.g.,User,Project)
Generated files:
@zitadel/proto: Modern ES modules inlogin/packages/zitadel-proto/- Local generation: Traditional protobuf files in
src/app/proto/generated/- TypeScript definition files (
.d.ts) - JavaScript files (
.js) - gRPC client files (
*ServiceClientPb.ts) - OpenAPI/Swagger JSON files (
.swagger.json)
- TypeScript definition files (
To generate proto files:
pnpm run generate
This automatically runs both generations in the correct order via Turbo dependencies.
Development Server
To start the development server:
pnpm start
This will:
- Fetch the environment configuration from the server
- Serve the app on the default port
Building
To build for production:
pnpm run build
This will:
- Generate proto files (via
prebuildscript) - Build the Angular app with production optimizations
Linting
To run linting and formatting checks:
pnpm run lint
To auto-fix formatting issues:
pnpm run lint:fix
Project Structure
src/app/proto/generated/- Generated proto files (Angular-specific format)buf.gen.yaml- Local proto generation configurationturbo.json- Turbo dependency configuration for proto generationprebuild.development.js- Development environment configuration script
Proto Generation Details
The Console app uses dual proto generation managed by Turbo dependencies:
Dependency Chain
The Console app has the following build dependencies managed by Turbo:
@zitadel/proto#generate- Generates modern protobuf files@zitadel/client#build- Builds the TypeScript gRPC client libraryconsole#generate- Generates Console-specific protobuf filesconsole#build- Builds the Angular application
This ensures that the Console always has access to the latest client library and protobuf definitions.
Legacy v1 API (Traditional Protobuf)
- Uses local
buf.gen.yamlconfiguration - Generates traditional Google protobuf JavaScript classes extending
jspb.Message - Uses plugins:
protocolbuffers/js,grpc/web,grpc-ecosystem/openapiv2 - Output:
src/app/proto/generated/ - Used for: Most existing Console functionality
Modern v2 API (ES Modules)
- Uses
@zitadel/protopackage generation - Generates modern ES modules with
@bufbuild/protobuf - Uses plugin:
@bufbuild/eswith ES modules and JSON types - Output:
login/packages/zitadel-proto/ - Used for: New user v2 API and services
Dependency Management
The Console's turbo.json ensures proper execution order:
@zitadel/proto#generateruns first (modern ES modules)- Console's local generation runs second (traditional protobuf)
- Build/lint/start tasks depend on both generations being complete
This approach allows the Console app to use both v1 and v2 APIs while maintaining proper build dependencies.
Legacy Information
This project was originally generated with Angular CLI version 8.3.20 and has been updated over time.