Skip to content

Publish results to STAC

Result publication uploads workflow output files to the configured result bucket and can optionally catalog their metadata in STAC. First configure the result bucket. These settings concern result publication, not publishing GitLab projects.

Choose catalog targets

STAC cataloging can use either or both of these targets:

  • A transactional STAC API, such as stac-fastapi with the Transactions extension. The API must be reachable and allow writes.
  • A static STAC catalog stored as JSON files in S3.

STAC settings do not disable uploads

Disabling both STAC targets skips cataloging, but the publication step still uploads output files to S3.

Configure publication through Helm

Enable the targets through Helm values. Replace the example STAC endpoint and metadata with your organization's settings; processor_url is your public UI URL.

configs:
  publish:
    catalog_static: true
    catalog: true
    stac:
      url: https://stac.example.com
      collection_prefix: antflow
      keywords: [antflow, processing]
      license: proprietary
      processor_name: AntFlow
      processor_url: https://antflow.example.com
      facility: My organization

Enable only the targets you need. collection_prefix defaults to the Helm release name when empty. For browser access to static catalogs, see Result delivery and Bucket CORS.

For the user-facing STAC contract, see STAC catalogs. For all publication settings, see the Helm chart reference.

Publication property prefix

The server setting publish.cwl_key defaults to publish in PublishSettings. It supplies the prefix for CWL property lookups such as publish:enabled, publish:catalog, and publish:catalog_static; it is not a workflow execution input. The keys are constructed dynamically from this prefix in the server.

Through the official Helm deployment, configure it under configs.publish:

configs:
  publish:
    cwl_key: publish

The underlying server configuration uses publish.cwl_key in YAML, or PUBLISH__CWL_KEY as an environment variable. The environment variable takes precedence over the YAML value. Leave the default unless your deployment needs a different property prefix.

See Workflow publication properties for the author-facing options and their interaction with platform settings. Use the platform's catalog and catalog_static settings to choose its STAC targets; disabling those targets does not disable S3 output uploads.