Skip to content

Improve in-code documentation for product asset graph#80

Merged
jirhiker merged 4 commits into
mainfrom
docs/product-asset-comments
Jun 26, 2026
Merged

Improve in-code documentation for product asset graph#80
jirhiker merged 4 commits into
mainfrom
docs/product-asset-comments

Conversation

@jirhiker

Copy link
Copy Markdown
Member

What

Documentation/comments only — no behavior change. Carries over the doc commit that landed on the #79 branch after that PR was merged.

Changes

  • orchestration/assets/products.py:
    • Refresh the stale module docstring — it predated the geoserver publish asset and GeoPackage flow; now includes the asset-graph diagram and the soft-fail / IO-manager design notes.
    • Add docstrings to all three asset builders (_build_source_asset, _build_combine_asset, _build_geoserver_asset) and build_product_assets.
    • Comment _in_name (combine-asset input kwargs must be valid Python identifiers).
    • Remove an unused is_summary local in the source-asset builder (dead code found during review).
  • orchestration/resources/die_config.py:
    • Document get_config's products.yaml → Config mapping.
    • Flag that the include-list source list must stay in sync with backend.config.SOURCE_KEYS, or include-list products silently drop sources.

Notes for reviewer

  • Verified orchestration.definitions still imports/loads after the dead-code removal.

🤖 Generated with Claude Code

- products.py: refresh stale module docstring (now covers the geoserver
  publish asset + GeoPackage flow and the ASCII graph), document all three
  asset builders and build_product_assets, explain _in_name sanitization,
  drop an unused is_summary local in the source-asset builder.
- die_config.py: document get_config's products.yaml -> Config mapping and
  flag that the include-list source list must track backend SOURCE_KEYS.

Docs/comments only; no behavior change.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Jun 26, 2026

Copy link
Copy Markdown

Your pull request is automatically being deployed to Dagster Cloud.

Location Status Link Updated
die-orchestration View in Cloud Jun 26, 2026 at 05:24 AM (UTC)

jirhiker and others added 3 commits June 25, 2026 23:15
Declare the Dagster dg CLI project layout: root pyproject marks the repo
as a dg project; orchestration/pyproject sets root_module=orchestration.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Document the dg-based workflow for Dagster operations (dev, list defs,
launch), the product asset-graph architecture, validation via the import
smoke test (dg check defs is currently blocked by a root_module layout
mismatch), and the Dagster+ serverless deploy setup.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
dg resolves a local module as <project_root>/<module_parts> on disk. With
the dg project at orchestration/ and root_module="orchestration", dg
looked for orchestration/orchestration/ (nonexistent), so `dg check defs`
failed and dg kept rewriting root_module to ".".

The orchestration package lives at repo-root level (./orchestration/) —
the same place the Dagster+ serverless build imports it from — so make
the repo root the dg project with root_module="orchestration", which
resolves to ./orchestration/. Remove the competing [tool.dg] block from
orchestration/pyproject.toml. Suppress the venv-mismatch warning (dg runs
via the orchestration venv through `uv run` while the project root is the
repo root).

`dg check defs` and `dg list defs` now succeed. Update AGENTS.md
accordingly.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@jirhiker jirhiker merged commit 7ce741a into main Jun 26, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant