Repository navigation
docs: trigger.type continuous, and --strict on a retargeted overlay patch (forge-cli #734) - #157
Merged
Merged
Conversation
…atch (forge-cli #734) builds-exposes-bindings.md gets a "Continuous builds: trigger.type: continuous" section: the example, that no scheduler starts the build, the refused trigger fields and their error, the 0.7.5 error, where the value belongs (the dbt and python runners refuse it, scaffold-composer still writes its nightly DAG), the overlay limitation and the stale-DAG note. The Flink section, the trigger.type list and the 0.7.6 fields list point to it, as do the Airflow pages that list the trigger types left out of fluid apply DAGs. validate.md's --env section shows overlay_patch_retargeted as a validation warning that --strict fails on, with --quiet, JSON, workspace mode, contract-validation, fluid test, overlay_entry_added and the bundle gap; test.md, contract-validation.md, environments-and-overlays.md and preview-fields.md point to it.
1 of 3 tasks
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Docs for forge-cli #734; merge after it:
trigger.type: continuous(schema 0.7.6 preview): a build its platform keeps running, which no scheduler starts, and which takes no other trigger.--strictfails on an overlay patch that lands on another entry (overlay_patch_retargeted), influid validate --env(and workspace mode),fluid contract-validation --envandfluid test --env.Every new statement is marked (unreleased, forge-cli #734). The generated
reference/contract-0.7.6-preview.mdis left alone; it is rebuilt from a released schema byscripts/gen_contract_reference.py.docs/concepts/builds-exposes-bindings.mdtrigger.type: continuoussection; the Flink section, thetrigger.typelist and "Fields that needfluidVersion0.7.6" point to it.docs/cli/validate.md--envand environment overlays" shows the retargeted patch as a validation warning, with--strict,--quiet, JSON, workspace mode,overlay_entry_addedand the bundle gap.docs/cli/test.md,docs/cli/contract-validation.md--strictcovers the overlay warning ("Environment overlay" row / categoryoverlay);--engine sodadoes not read--strict.docs/concepts/environments-and-overlays.mdoverlay_patch_retargetedbullet says the commands now report it.docs/reference/preview-fields.mdengine: flinkone.docs/advanced/airflow.md,docs/walkthrough/airflow-declarative.md,docs/cli/generate-artifacts.mdfluid applyDAG.Output blocks are copied from the CLI on the #734 branch.
Checks (local)
scripts/check_cli_docs.pyagainst the pinned CLI (data-product-forge 0.18.1): all six checks OK (1332 documented invocations, version sweep).scripts/check_providers.py,scripts/gen_contract_reference.py --check: OK.npm run docs:build, thennode scripts/check-dist-links.mjs: clean (137,867 references, 242 pages); the two new anchors exist in the built HTML.🤖 Generated with Claude Code