Skip to content

docs(spark): a Spark job is granted its own table where Lake Formation governs new tables (forge-cli #1010) - #270

Merged
fas89 merged 2 commits into
mainfrom
claude/docs-lf-wave17
Nov 19, 2026
Merged

fas89 merged 2 commits into
mainfrom
claude/docs-lf-wave17

Conversation

@fas89

@fas89 fas89 commented Nov 19, 2026

Copy link
Copy Markdown
Collaborator

Summary

Documents forge-cli #1010, on main (d863e3d8) after the 0.33.0 cut and in no release: a Spark job's role is granted Lake Formation access to the table it writes where Lake Formation governs new tables, also for an output whose binding declares no governance.lakeFormation.

  • advanced/spark-iceberg-aws.md: a new subsection of "Lake Formation writes", "A job's grant on its own table" (what 0.33.0 did, the grant and its count that the plan decides from the account's Lake Formation settings, the module forge emits for the example contract, which outputs and runtimes get it, and the new permission lakeformation:GetDataLakeSettings), a sentence in the "A dead-letter table" row of "What forge provisions", and one in the dead-letter section and the dead-letter bullet of "Lake Formation writes".
  • upgrading.md: one bullet under "Not in a release yet".

Related CLI PRs

Areas Updated

  • Getting Started
  • CLI Reference
  • Provider Docs
  • Walkthroughs / Examples
  • Contributing / Community Docs
  • Other: advanced guide, upgrading

Decisions

  • The markers read *On forge-cli main, not yet in a release ([forge-cli #1010](...)).*: the pull request merged after the 0.33.0 cut. The pin stays at 0.32.0.
  • The module shown is real: fluid generate iac's emitter run on the page's example contract on EMR Serverless, on main after the merge. On 0.33.0's code the same contract emits no grant and no settings (run), which is the statement of the first sentence.
  • The new sentences are in a subsection of their own and not in the list about registerLocation: the reviewer pointed out that the list's intro scopes it to a contract that registers a location, and the new grant needs no registration.
  • Not run: a tofu plan against an account with each setting. The count rule is read from the emitted expression and from the pull request's plan test; the data source is the Terraform AWS provider's, which calls GetDataLakeSettings (read in its source).

Checklist

  • python scripts/check_cli_docs.py (with forge-cli's live CHANGELOG.md), check_providers.py and gen_contract_reference.py --check pass
  • Site build, built-link check, offline link check and the linked anchors pass locally

Notes

  • A reviewer checked 32 sentences against the code, with 50 runs; every sentence the first draft added held. Its three findings were nearby sentences that read as the current rule (the dead-letter sentence of the dead-letter section, the dead-letter bullet, and the scope of the section's intro): they are fixed.
  • The code of #1010 on main equals the code the text was written and reviewed against (the pull request's head ac814008) for every file but the changelog.
  • Docs main (docs(spark): a run starts only on the job config fluid apply compiled (forge-cli #1014) #268) is the base.

…n governs new tables (forge-cli #1010)

The grant and its plan-time count, the module forge emits, and the permission the identity that plans needs.

This branch was previously deployed

1 inactive deployment
github-pages — c426b160 Deployed Nov 19, 2026 by fas89 via deploy #423
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