content-store

/content-store — Custom Content Store Generator

In-Process SDK only — content stores deploy inside the ACS JVM as part of the Platform JAR. The repository reads/writes all binaries through the ContentService, which delegates to the configured content store. Never read or write files on the local filesystem directly — go through the store's ContentReader/ContentWriter.

Generate a custom content store connector from requirements.

Input

Read REQUIREMENTS.md to identify content store requirements:

1. Resolve the Platform JAR project's Root path from Section 2 (Project Architecture).

   • If Section 2 contains no Platform JAR project, stop and explain that /content-store only applies to the in-process Platform JAR project.

2. Read the "Content store requirements" sub-section (Section 8 Deployment Requirements or a dedicated storage section).

   • If none are present, stop and ask the user to run /requirements first (or provide a description as $ARGUMENTS).
   • Identify the store shape: a brand-new backing store (extends AbstractContentStore), or a wrapper over the default store (caching / encrypting / aggregating).

3. From Section 2, derive:

   • {platform-project-root} — . for Platform JAR only mode; {name}-platform/ for Mixed mode
   • {module-id} — the Platform JAR artifactId (bare artifact ID, e.g. my-extension). Read from <artifactId> in the platform pom.xml or derive as {platform-artifactId} from Section 2. Never use the full module.id property value as the directory name.
   • {java-package} — the Java package declared in Section 2
   • {prefix} — the namespace prefix declared in Section 5 (Content Model Requirements)

4. Derive from content store requirements:

   • {Store} — PascalCase store name (e.g. S3, Encrypted, Tiered)
   • {store-root-property} — the configurable root location property (e.g. dir.contentstore.{prefix})
   • Whether the store wraps another store (composition) or is a standalone backing store