Repository navigation
docs(spark): a Spark job is granted its own table where Lake Formation governs new tables (forge-cli #1010) - #270
Merged
Merged
Conversation
…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.
…-wave17 # Conflicts: # docs/upgrading.md
5 of 8 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
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 nogovernance.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 itscountthat 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 permissionlakeformation: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
Decisions
*On forge-climain, 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.fluid generate iac's emitter run on the page's example contract on EMR Serverless, onmainafter 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.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.tofu planagainst an account with each setting. Thecountrule is read from the emitted expression and from the pull request's plan test; the data source is the Terraform AWS provider's, which callsGetDataLakeSettings(read in its source).Checklist
python scripts/check_cli_docs.py(with forge-cli's liveCHANGELOG.md),check_providers.pyandgen_contract_reference.py --checkpassNotes
mainequals the code the text was written and reviewed against (the pull request's headac814008) for every file but the changelog.main(docs(spark): a run starts only on the job config fluid apply compiled (forge-cli #1014) #268) is the base.