Goal
We would like to allow CRSs to maintain some sort of knowledge base across runs. We will leave the format of the knowledge base up to the CRS's discretion (as long as it's regular files and directories).
This acts like a dedicated allocation space for a CRS to arbitrarily write to, and provides read-only history of previous CRS runs that have written to their allocated space.
Proposal
Let's denote this knowledge base as "ledger". The ledger is a directory in which the CRS may write any number of files or subdirectories to.
OSS-CRS shall expose a directory of previous or parallel runs' ledgers as read-only, and expose a writable ledger for the CRS to use.
For convenience, OSS-CRS can symlink a "latest" ledger for the most recent run-id.
All of the state is maintained in .oss-crs-workdir. However, instead of delimiting on the compose.yaml, project, or harness, the ledgers should only delimit on the CRS name, as registered.
libCRS API considerations TODO.
No changes needed to oss-crs CLI.
Goal
We would like to allow CRSs to maintain some sort of knowledge base across runs. We will leave the format of the knowledge base up to the CRS's discretion (as long as it's regular files and directories).
This acts like a dedicated allocation space for a CRS to arbitrarily write to, and provides read-only history of previous CRS runs that have written to their allocated space.
Proposal
Let's denote this knowledge base as "ledger". The ledger is a directory in which the CRS may write any number of files or subdirectories to.
OSS-CRS shall expose a directory of previous or parallel runs' ledgers as read-only, and expose a writable ledger for the CRS to use.
For convenience, OSS-CRS can symlink a "latest" ledger for the most recent run-id.
All of the state is maintained in
.oss-crs-workdir. However, instead of delimiting on thecompose.yaml,project, orharness, the ledgers should only delimit on the CRS name, as registered.libCRSAPI considerations TODO.No changes needed to
oss-crsCLI.