Most bug fixes, doc enhancements, and small, incremental improvements for AWS CloudFormation Guard can be surfaced and resolved via GitHub issues and pull requests. However, any suggestions for substantial changes to the ruleset langauge or tooling should be documented and actioned upon via a request for comments (RFC). This will provide a standardized process for discussion of major improvements to the tooling and ruleset language.

This goes over the official process for creating, drafting, reviewing, and seeing an RFC to completion.

Use RFC template in this directory to guide your RFC. This has the basic structure of what we are expecting for RFCs. The RFC should highlight the motivation for the changes, a detailed design/description of that the changes entail, and considerations for not

Submit a Pull Request to the AWS CloudFormation Guard repository. The pull request will be reviewed by CloudFormation team members and open source contributors.

Once the PR for the RFC is created, the RFC will undergo revisions similar to any other Guard PR until any and all concerns are addressed and the PR reaches a terminal state (accepted/rejected).

If approved, the RFC has been accepted for enhancement, and work can begin to accomplish what is set out in the PR. Accepted PRs will be kept in the repo for reference.