fluid export-opds
Export a FLUID contract to an OPDS (Open Data Product Specification) JSON file in one shot.
Syntax
fluid export-opds CONTRACT [--env ENV] [--out PATH]
Key options
| Option | Description |
|---|---|
CONTRACT | Path to the FLUID contract (typically contract.fluid.yaml). |
--env | Overlay environment to apply before exporting. |
--out | Output path for the generated JSON. Default runtime/exports/product.opds.json. |
Examples
fluid export-opds contract.fluid.yaml
fluid export-opds contract.fluid.yaml --env prod
fluid export-opds contract.fluid.yaml --out exports/customer360.opds.json
Notes
- This is a thin convenience wrapper that always writes to a file. For interactive workflows, validation, or stdout output use
fluid odpsinstead. - Internally it calls
OdpsProvider.to_odps(). If the provider import fails it falls back to a minimal envelope containingid,title,owner,domain, andexposes. - The output directory is created automatically.
- See also
fluid odps-bitolfor Bitol.io's ODPS variant andfluid odcsfor the Open Data Contract Standard.