Dashboard › institutional-transition-lab › Distillation
ef5705d1-a34d-4f21-9b9c-670435508a2c["lore_tm_v1_HqODlTEQgqNVPsAvfoshjUl53PV6QFqIpXCFjyQ1A1s"]
opentofu-github-pr-2953 says governance references and materials were moved to the new opentofu/org repository; metadata shows 43 changed files, merged at 2025-06-25T17:50:10Z, merge commit 75bf1c2f65ad4baabd51a5e88873f805f5b2a1c7, base SHA 3c170157023ac1290c89567ce432c35aa185099a, and head SHA 5f5705b8947cd62834733e6c20635d8d13a616dd.opentofu-github-pr-2953 patch patch:0 replaces the complete local Technical Charter—including TSC oversight, membership, voting, policy, licensing, and amendment provisions—with a link to https://github.com/opentofu/org/blob/main/CHARTER.md.opentofu-github-pr-2953 patch patch:1 replaces the complete local governance document with a link to https://github.com/opentofu/org/blob/main/GOVERNANCE.md; the removed document specified new TSC members require nomination plus a two-thirds supermajority, inactivity removal requires a majority after 3 consecutive inactive months and 14 days’ notice, removal for cause requires a two-thirds vote excluding the affected member, and voluntary resignation requires no vote.opentofu-github-pr-2953 also stated: 1. the TSC has ultimate authority over all projects in the OpenTofu organization; 2. it may delegate project decision-making authority to maintainers through an explicit documented TSC vote, with delegated projects maintaining MAINTAINERS.md; 3. it retains the right to overrule delegated decisions; 4. formal external-project relationships are established by TSC vote; 5. governance amendments require a two-thirds vote of the entire TSC plus LF Projects approval.opentofu-github-pr-990 adds the TSC summary for 2023-12-05; metadata shows 1 changed file, merged at 2023-12-11T11:52:31Z, merge commit 6b864ef262d6b924d94a61a0e1e29ff27b834a02, base SHA 5fc6ba240dbbe6ecc3643040150686f88e223583, and head SHA 7db41d4cfbbd4c54cfd9db70c3d58282a0118bb3.opentofu-github-pr-990 patch lists 2023-12-05 attendees Igor Savchenko (@DiscyDel, linked as @DicsyDel), Marcin Wyszynski (@marcinwyszynski), Roger Simms (@allofthesepeople), and Roni Frantchi (@roni-frantchi); absent were Yevgeniy Brikman (@brikis98) and Omry Hary (@omry-hay).opentofu-github-pr-990: 1. unanimously change the default registry namespace to opentofu; 2. do not prioritize a registry UI/docs solution that quarter, but invite RFCs and re-examine proposed options; 3. accept the client-side state encryption RFC as a higher-priority differentiating feature and “pull up” the work; 4. potentially accept OpenTofu VS Code Language Server support, but do not assign core-team follow-up or higher priority; 5. accept PR #799, “Implement gunzipbase64”; 6. accept PR #579, “Fix filesystem state backend to be fast.”opentofu-github-pr-990: Roni Frantchi favored prioritizing a UI so users could identify OpenTofu-supported packages without relying on HashiCorp Terraform materials; Igor Savchenko preferred not to divert the core team and disclosed work on library.tf, envisioned as a neutral registry for Terraform, OpenTofu, and other IaC; Roger Simms suggested UI/docs through the CLI; Marcin Wyszynski considered it non-priority. The vote was Roni “Yes,” everyone else “No.”terraform-github-issue-22468 describes Terraform 0.11.14 use across a multi-cloud, multi-region platform with hundreds of tenants spanning hundreds of AWS accounts and GCP projects, shared tenancy/ownership, ignore_changes, targeted applies, and a CI pipeline containing hundreds of Terraform installations.-target applies in some circumstances to get a job done.vpc_flow_logs resource.-target mode that evaluates whether proposed changes exceed the requested target and fails gracefully for investigation rather than applying out-of-scope changes.terraform plan, verifies that changes affect only resources named in the original -target, and proceeds with applying the plan only on that basis; they would prefer Terraform to perform this check.terraform-github-issue-34139 reports Terraform 1.6.0 x64 failing while retrieving azuread_access_package_assignment_policy.this with HTTP 403 and OData UnAuthorized: User is not authorized to perform the operation. Reason: Unauthorized.terraform-github-issue-34139 configuration makes azuread_access_package_assignment_policy.this depend on azuread_access_package.this, azuread_access_package_resource_catalog_association.this, and azuread_access_package_resource_package_association.this; expected order is catalog association creation, resource-package association creation, then assignment-policy creation.terraform-github-issue-34139 states an Azure DevOps pipeline service role has Identity Governance Administrator and Directory.ReadWrite.All; the pipeline successfully creates a new catalogue and AAD group, then fails during access-package policy association because the referenced object ID is reported unauthorized. IDs and references were replaced with x for security.