IntenseWebs/opentofu
3
0
Fork 0
mirror of https://github.com/opentofu/opentofu.git synced 2024-12-23 07:33:32 -06:00
Code Issues Packages Projects Releases Wiki Activity
08ad2f5983
opentofu/rfc
History
Martin Atkins e6ca786e09 rfc: Static Evaluation of Provider Iteration further updates 
This continues the work of the last few commits, updating this RFC to
reflect the evolved design that's makes room for adding fully-dynamic
provider instance expansion in a later release.

Signed-off-by: Martin Atkins <mart@degeneration.co.uk>
2024-10-31 10:50:34 -07:00
..
20240513-static-evaluation Fix typos (#1905) 2024-08-29 13:20:33 -04:00
20230905-provider-gpgkey-missing.md Backfill accepted RFCs into new location (#1702) 2024-06-12 07:31:35 -04:00
20231017-homebrew-like-registry-design.md Backfill accepted RFCs into new location (#1702) 2024-06-12 07:31:35 -04:00
20231106-registry-repository-folder-structure.md Fix typos (#1905) 2024-08-29 13:20:33 -04:00
20231107-registry-gpg-key-verification.md Backfill accepted RFCs into new location (#1702) 2024-06-12 07:31:35 -04:00
20231108-registry-automatic-version-bumping.md Backfill accepted RFCs into new location (#1702) 2024-06-12 07:31:35 -04:00
20231109-registry-response-generation.md Backfill accepted RFCs into new location (#1702) 2024-06-12 07:31:35 -04:00
20231114-client-side-state-encryption.md Backfill accepted RFCs into new location (#1702) 2024-06-12 07:31:35 -04:00
20231123-registry-submission-via-github-issues.md Backfill accepted RFCs into new location (#1702) 2024-06-12 07:31:35 -04:00
20240513-static-evaluation-providers.md rfc: Static Evaluation of Provider Iteration further updates 2024-10-31 10:50:34 -07:00
20240513-static-evaluation.md RFC #1042: Planning the implementation of static evaluation (#1649) 2024-06-12 09:21:32 -04:00
20240524-OpenTofu-RFC-Process.md New RFC process (#1669) 2024-06-03 10:30:18 -04:00
20240529-OpenTofu-Specific-Code-Override.md RFC: OpenTofu Specific Code Override (#1699) 2024-06-17 13:35:42 +03:00
20240725-exclude-resources.md RFC: -exclude flag for planning and applying (#1860) 2024-08-08 09:31:36 -04:00
README.md Fix RFC template link (#1821) 2024-07-15 14:07:56 -04:00
yyyymmdd-template.md New RFC process (#1669) 2024-06-03 10:30:18 -04:00

README.md

The OpenTofu RFCs

This folder contains Request For Comment (RFC) documents that have been discussed, reviewed, and accepted. They represent a proposal of changes to one or more of the repositories in the OpenTofu organization.

RFCs are primarily created by the OpenTofu Community in response to one or more GitHub issues that require a more in-depth discussion than the GitHub Issue process can provide. They are organized by date to help show the progression of concepts over time.

Authoring an RFC

When an Issue is given the needs-rfc label, any community member may propose an RFC by following these steps:

  1. Copy the yyyymmdd-template.md to ./rfc/${isodate}-${rfc title}.md on a branch in their fork of the OpenTofu Repository
  2. Edit the newly created Markdown file and fill in the template fields
  3. Submit a Pull Request in the OpenTofu Repository, linked to the open issue(s)

Note

It's ok to file an incomplete RFC. Please submit it as a draft pull request to get early feedback.

Once an RFC is submitted, community members discuss the RFC in detail until all open questions are resolved

To Accept an RFC, the majority of the OpenTofu Core Team must approve the Pull Request. If a consensus is not reached, the Pull Request is closed and the Core Team may ask for a new RFC or close the original issue entirely.

Once an RFC is Accepted and Merged, the Core Team creates issues in the relevant repositories to track the work required to implement the RFC.

Amending an RFC

RFCs are not set in stone, Approval signifies that an initial consensus has been reached and work can be started. If you realize that parts of the implementation won't work, feel free to amend the RFC in a subsequent PR. Doing so will serve as an important point of discussion if something doesn't go according to plan.