Back to Terraform Provider Aws

Design Decision Log

docs/design-decision-log.md

6.43.03.7 KB
Original Source
<!-- Copyright IBM Corp. 2014, 2026 --> <!-- SPDX-License-Identifier: MPL-2.0 -->

Design Decision Log

This serves as an index over the various decisions we make as a maintainer team over what is considered best practice, and what we should encourage/require as a design standard. These are not necessarily fixed, and are likely to evolve and be replaced as new decisions are made. This is an evolution of an internal process and will pivot to take place in public as much as possible to allow for external feedback from the community and core contributors.

DecisionDescriptionIssue Link
Relationship Resource Design StandardsAlign on design standards for relationship management resources in the Terraform AWS Provider.#9901
SecretsManager Secret Target AttachmentAssess the feasibility of replicating the AWS::SecretsManager::SecretTargetAttachment CloudFormation function with Terraform.#9183
RDS Blue Green DeploymentsAssess the feasibility extending blue green deployment functionality found in aws_rds_instance to aws_rds_cluster.#28956
Exclusive Relationship Management ResourcesA proposal describing the use case for "exclusive relationship management" resources and their function within the Terraform AWS provider.#39203
Standardize Use of the id AttributeDefine a standard for use of the "id" attribute given improvements to provider development and testing libraries have removed its requirement.#37628
Use plancheck.ExpectResourceAction with disappears acceptance testsAcceptance tests exercising out of band deletion (colloquially named "disappears" tests) should utilize the terraform-plugin-testing library's plancheck package to assert expected post apply actions.N/A
Supporting module-scoped User-Agents with provider_metaA proposal for implementing provider_meta support and aligning the standard and AWSCC provider implementations.#45464
Migration from go-changelog to ChangieMigrate CHANGELOG generation from go-changelog to Changie for improved automation, better developer experience, and support for complex release workflows including beta/GA cycles.N/A