The SOCI CLI is currently a mix of build time tooling, runtime tooling, and debugging tooling. Each of these components have a range of "production readiness" with the debug tooling being the least mature, then runtime tooling, then build time tooling. This makes it hard for the community to know whether they can expect stability if they deploy the CLI as part of their production pipelines.
A design document describing which parts of the CLI we intend to stabilize, which parts are intended to be replaced with other tooling, and which parts are intentionally unspecified as we see which way the community takes them.
Describe any alternative solutions/features you've considered
No response
Any additional context or information about the feature request
turan18
commented
11 months ago
Description
The SOCI CLI is currently a mix of build time tooling, runtime tooling, and debugging tooling. Each of these components have a range of "production readiness" with the debug tooling being the least mature, then runtime tooling, then build time tooling. This makes it hard for the community to know whether they can expect stability if they deploy the CLI as part of their production pipelines.
Our official statement is that the CLI is unstable, but it would be good to add some clarity around what our intentions are.
Describe the solution you'd like
A design document describing which parts of the CLI we intend to stabilize, which parts are intended to be replaced with other tooling, and which parts are intentionally unspecified as we see which way the community takes them.
Describe any alternative solutions/features you've considered
No response
Any additional context or information about the feature request
No response