store-module-architecture

The BK-CI Store module architecture defines how plugins, templates, and container images are published, audited, installed, and managed across their lifecycle within the R&D Store.

The Store module organizes lifecycle management through submodules like api-store, biz-store, model-store, and boot-store, which separate interface definitions, business logic, data models, and service bootstrapping.

To extend BK-CI Store components, refer to the submodule structure under src/backend/ci/core/store/ and locate relevant data models like T_ATOM, T_TEMPLATE, and T_IMAGE as your implementation starting point.

Yes, the Store module explicitly supports managing container images alongside plugins and templates, handling their publishing, auditing, installation, and statistics using the T_IMAGE data model.

When building BK-CI Store features, you need to know the core data models T_ATOM for plugins, T_TEMPLATE for templates, and T_IMAGE for container images to align with architecture conventions.

Refer to the Store module architecture guide when building or extending Store functionalities, ensuring your development and maintenance tasks align with established architectural conventions and data models.