Dashboard › institutional-transition-lab › Distillation
5b1507e6-8dfc-439a-b26a-6aac6cdda932["lore_tm_v1_16KgcAEy1oLgx_DBEEQtOTLa5_9Y-F8L9OkC0w47s0U","lore_tm_v1_H3GM2OVXs9PWuRWSB2iahjpyvqEYTiUxYs8dKFoCM74","lore_tm_v1_wyOiLSMQCtQuhrduC8lDbxXghmnurhIEzX0U3bSfMvM","lore_tm_v1_ccj67woJUAcJ5NU2R70ZOrDr9rM7CwqRKKQO4CeRaIo","lore_tm_v1_HykwJ6uuiRhxXQj9oMh_9ZPX_OdP7hHuFGCmwXEXng4","lore_tm_v1_3jqZwOpSeVT3pIslXZMjSO6gFm13kIp8kAzeuJm3NFE","lore_tm_v1_WbXdeZ_5d10jvVqkTKcS9_m_V28-mVkh3__OOMAXKxs","lore_tm_v1_5uB1lJhmpcAjuMTftj-V7i9kJTpgO4-DLJ61MyiBHJ4","lore_tm_v1_kHbvVIIl-6JtWnax--r0OjYBiFiI0ttE2dp1CUbhWiU","lore_tm_v1__0XsOtzQ-2NH-sHm9yVsPprAU6a9FLS3mxurvjYjb5I","lore_tm_v1_n9XVPyW5W4jHNRAdELPwrB4_hb7TesdegBWq3JMZGsw","lore_tm_v1_dbRGHfy37lDKg_HH0Q23VtebLCXixCQzQB_BXP9RFMU","lore_tm_v1_YFAczjQdI-oXWkFxZBjbdv1IuCMgfY0aUFmUsTKBZm8","lore_tm_v1_BMdR16K54NG2x6VBKCJpOZJ_i6e1ehA5zWVq2ZkbI7A","lore_tm_v1_DujglF0pswVbclATsm31jcfdH3XA_wduWxdW5kE_pDE","lore_tm_v1_N6NHFXeHfq6ppPBm2ZAfDUp7y2jJDNy9d3GRHu02DUk"]
opentofu-github-pr-2959 says CODEOWNERS was not working after a governance-chart change because the new team is named opentofu-maintainers; the proposed fix was to update CODEOWNERS. PR metadata: 1 changed file, head 6c1afd075a69497c77a5341eb47162aeacb8f67f, merge commit b82ed64756670f0ff54f034120d1e71aefa21358, merged. No implementing patch was supplied. (meaning Jun 25, 2025)opentofu-github-pr-3559 updates the support policy in RELEASE.md following the @opentofu/technical-steering-committee meeting on 09-12-25. PR metadata: 1 changed file, head d06503ad9f725637a690bf9348bcff1f6ade528f, merge commit b2c6b935e06bfca47662792e7f71a7df8a6a36ad, merged. No implementing patch or policy terms were supplied. (meaning Dec 9, 2025)opentofu-github-pr-3473 is an open RFC in rfc/20251021-databricks-backend.md proposing a Databricks state backend using Unity Catalog volumes and Databricks Unified Auth, with locking through Databricks Lakebase (recommended) or Delta Lake (fallback). Motivation: avoid lack of cloud-storage backends, duplicate cloud-IAM versus Unity Catalog RBAC/ABAC controls, separate audit trails, and operational complexity. (meaning Nov 5, 2025)host, catalog, schema, volume, and key; example values are https://workspace.cloud.databricks.com, terraform_state, production, infrastructure, and terraform.tfstate. Optional defaults/configuration: lock_backend = "lakebase" or "delta", lock_timeout = "10m", and token = "${env:DATABRICKS_TOKEN}"; omitted authentication uses the SDK auth chain./Volumes/{catalog}/{schema}/{volume}/{key}, accessed through the Databricks Files API/SDK, versioned by underlying cloud storage, and protected by cloud-provider encryption with optional client-side encryption.delta-kernel-rs identified as a potentially very cheap access method.~/.databrickscfg.databricks catalogs create terraform_state; 2. databricks schemas create production terraform_state; 3. databricks volumes create terraform_state production infrastructure MANAGED; 4. update backend configuration; 5. run tofu init -migrate-state.internal/backend/remote-state/databricks. Backend contains client *databricks.WorkspaceClient, catalog, schema, volume, and lockBackend; required methods are StateMgr(workspace string) (statemgr.Full, error), Workspaces() ([]string, error), and DeleteWorkspace(name string, force bool) error.429, and no retry for authentication failures.VARIANT column; 3. S3/Azure/GCS plus Unity Catalog metadata—proven and cheaper, but does not unify governance.opentofu-github-pr-4018 implements a compromise for warning about forthcoming removal of official 32-bit CPU support: mark only official GitHub Actions release builds, then warn only from tofu init on 386 or arm, avoiding warnings in third-party builds and repeated warnings on every tofu plan/tofu apply. The original body called the support decision a draft not yet discussed by maintainers; the PR was later merged as commit 82676082728b0dc5fb14552f2a663850d7422817. (meaning Aug 11, 2026).github/workflows/release.yml sets BUILD_OPENTOFU_OFFICIAL: '1' in the official release workflow. New file version/official.go defines package-global officialBuild, IsOfficialBuild() bool, and test helper WithFakedOfficialBuild(official bool, f func()); official status is injected with -X 'github.com/opentofu/opentofu/version.officialBuild=1'. The helper temporarily modifies global state, restores it with defer, and must not be used in parallel tests.opentofu-github-pr-727 adds # SPDX-License-Identifier: MPL-2.0 to .github/scripts/compare-release-versions.sh. The 1-file PR merged as 131b15c45e373c743648b0059d022b58b2f53251; the change was explicitly described as not user-facing. (meaning Oct 15, 2023)opentofu-github-pr-823 adds TSC_SUMMARY.md for the Nov 2, 2023 meeting. Attendees: Igor Savchenko (@DiscyDel, linked as DicsyDel), Marcin Wyszynski (@marcinwyszynski), Roger Simms (@allofthesepeople), and Roni Frantchi (@roni-frantchi). Absent: Yevgeniy Brikman (@brikis98) and Omry Hary (@omry-hay). (meaning Nov 2, 2023)#741. Reasons, in order: 1. keep the core team focused on the CLI instead of a highly available mission-critical SaaS; 2. maximize availability using GitHub/AWS; 3. make the registry transparent as a Git repository; 4. decouple artifact resolution from documentation and signing so each can evolve to separate non-functional requirements.@RLRabinowitz and @cube2222 to announce the RFC and detail scraping of modules/providers/keys, key submission, version bumps, the design document, and core-team task scope.7:30PM CET, with exact time assigned to @allofthesepeople; agenda items must be posted at least 24h ahead or the meeting is canceled.opentofu-github-pr-990 adds the Dec 5, 2023 TSC summary. Attendees: Igor Savchenko, Marcin Wyszynski, Roger Simms, and Roni Frantchi. Absent: Yevgeniy Brikman and Omry Hary. (meaning Dec 5, 2023)opentofu; 2. do not prioritize registry UI/docs that quarter—Roni voted yes, everyone else no, but RFCs for UI options were invited; 3. unanimously accept and prioritize client-side state encryption RFC #874; 4. do not prioritize OpenTofu support in the VS Code Language Server (#970), though the RFC could be accepted without core-team follow-up; 5. unanimously accept gunzipbase64 PR #799; 6. unanimously accept filesystem-backend performance PR #579.library.tf, envisioned as an unaffiliated Terraform/OpenTofu/other-IaC registry; Roger preferred CLI-based UI/docs; Marcin had no strong opinion and did not consider it a priority.#874 was viewed unanimously as highly requested and differentiating. Marcin preferred the long-term principle of not storing secrets in state but judged the intermediate encryption solution better than no solution.gunzipbase64 PR #799 was accepted because it is the inverse of an existing function and analogous functions have counterparts, while the longer-term preference remained custom function extensions/reuse.-target applies in some circumstances to get a job done.ignore_changes to limit updates Terraform detects and sometimes need -target applies for specific changes.vpc_flow_logs; only the VPC flow logs should change.terraform plan, verify changes are limited to the originally targeted resources, and only then apply.terraform-github-issue-22468 requests a strict targeting mode that refreshes and evaluates dependencies but fails gracefully if a planned operation would change anything outside -target; desired semantics were: “no, really dont change anything other than what ive told you, and if you cant do that, or feel uncomfortable about it, then bail out.” The reported version was Terraform 0.11.14, probably affecting all versions. (meaning Aug 14, 2019)terraform-github-issue-34139 reports Terraform 1.6.0 x64 failing to create azuread_access_package_assignment_policy.this[0] in an Azure DevOps pipeline with HTTP 403, OData error: UnAuthorized, despite dependencies on azuread_access_package.this, azuread_access_package_resource_catalog_association.this, and azuread_access_package_resource_package_association.this.34139, expected order was catalog association creation, resource-package association creation, then assignment-policy creation. Actual behavior failed while retrieving the assignment policy by object ID. The pipeline service role had Identity Governance Administrator and Directory.ReadWrite.All; catalog and AAD-group creation succeeded before policy association failed. IDs were redacted for security. (meaning Oct 25, 2023)opentofu-github-pr-2953 unanimously abstained: all recognized relocation of governance documents/TSC notes to opentofu/org but found no demonstrated organizational-rights change. Luna A/B used event_kind: "reorganization" and effective date Jun 25, 2025; Terra left event/date null. All cited incomplete evidence, although their ambiguity text differed on whether omitted patches made the conclusion uncertain.opentofu-github-pr-2959 unanimously returned record_class: "abstain", event_kind: "control_rights", and no power edges because the merged PR lacked an implementing patch that could verify actual CODEOWNERS rights or scope.opentofu-github-pr-3473 both classified it as record_class: "control_event" and event_kind: "product" with no power changes; Terra had no response.opentofu-github-pr-3559 disagreed: Luna A classified the undocumented RELEASE.md update as no_event; Luna B and Terra classified it as a product control_event. All noted that no patch/policy terms established an organizational-rights change.opentofu-github-pr-4018 diverged: Luna A/B treated merged official-build detection as a product control_event, while Terra treated ending official 32-bit support as a proposal_only control-rights edge removing the OpenTofu project’s release support for 32-bit architectures. Luna A called the patch/body relation patch_supersedes_body; Luna B and Terra called it consistent.opentofu-github-pr-727 classified the merged MPL-2.0 SPDX addition as an effective_institutional_change, event_kind: "license", with an effective license edge over compare-release-versions.sh; Terra classified it as no_event with no edge.opentofu-github-pr-823 as a strategy control_event with no power changes, focusing on selection of the registry RFC and deferral of user-facing registry design; these frozen responses did not capture the separate staffing/funding reorganization in the same patch.opentofu-github-pr-990 as a control_event with no power changes. Luna A used event_kind: "strategy" for the broad TSC summary; Luna B and Terra used event_kind: "product" focused on the default registry namespace decision. Both Luna B and Terra noted that the summary records a decision but does not show implementation.terraform-github-issue-22468 both returned no_event, no event kind, and no power changes; Terra had no response.terraform-github-issue-34139 disagreed: Luna A treated the Azure authorization failure as a product control_event; Luna B and Terra treated it as no_event. All supplied no power changes.opentofu-github-pr-823 and began validating the revision and verbatim evidence.