docs/provider: Whitespaces at the end of line fixes. (#14954)

Co-authored-by: Janos Feher <git@janosfeher.com>

.github/workflows/changelog.yml

@@ -25,7 +25,7 @@ jobs:
         with:
           msg: |-
             Thank you for your contribution! :rocket:
-            
+
             Please note that the `CHANGELOG.md` file contents are handled by the maintainers during merge. This is to prevent pull request merge conflicts, especially for contributions which may not be merged immediately. Please see the [Contributing Guide](https://github.com/terraform-providers/terraform-provider-aws/blob/master/.github/CONTRIBUTING.md) for additional pull request review items.
 
             Remove any changes to the `CHANGELOG.md` file and commit them in this pull request to prevent delays with reviewing and potentially merging this pull request.

.github/workflows/dependencies.yml

@@ -29,7 +29,7 @@ jobs:
           check_duplicate_msg: true
           msg: |-
             Thank you for your contribution! :rocket:
-            
+
             Please note that typically Go dependency changes are handled in this repository by Renovate Bot or the maintainers. This is to prevent pull request merge conflicts and further delay reviews of contributions. Remove any changes to the `go.mod`, `go.sum`, and `vendor/` files and commit them into this pull request.
 
             Additional details:

.github/workflows/snapshot.yml

@@ -1,6 +1,6 @@
 name: Snapshot
 
-on: 
+on:
   schedule:
     - cron: '15 5 * * *'
   workflow_dispatch:

README.md

@@ -2,7 +2,7 @@
     <img src="https://cdn.rawgit.com/hashicorp/terraform-website/master/content/source/assets/images/logo-hashicorp.svg" alt="Terraform logo" title="Terraform" align="right" height="50" />
 </a>
 
-# Terraform Provider for AWS 
+# Terraform Provider for AWS
 
 [![Forums][discuss-badge]][discuss]
 
@@ -15,7 +15,7 @@
 - Chat: [gitter](https://gitter.im/hashicorp-terraform/Lobby)
 - Mailing List: [Google Groups](http://groups.google.com/group/terraform-tool)
 
-The Terraform AWS provider is a plugin for Terraform that allows for the full lifecycle management of AWS resources. 
+The Terraform AWS provider is a plugin for Terraform that allows for the full lifecycle management of AWS resources.
 This provider is maintained internally by the HashiCorp AWS Provider team.
 
 Please note: We take Terraform's security and our users' trust very seriously. If you believe you have found a security issue in the Terraform AWS Provider, please responsibly disclose by contacting us at security@hashicorp.com.

ROADMAP.md

@@ -1,112 +1,112 @@
 # Roadmap: August - October 2020
- 
+
 Every few months, the team will highlight areas of focus for our work and upcoming research.
- 
+
 We select items for inclusion in the roadmap from the Top 10 Community Issues, [core services](docs/CORE_SERVICES.md), and internal priorities. When community pull requests exist for a given item, we will prioritize working with the original authors to include their contributions. If the author can no longer take on the implementation, HashiCorp will complete any additional work needed.
- 
+
 Each weekly release will include necessary tasks that lead to the completion of the stated goals as well as community pull requests, enhancements, and features that are not highlighted in the roadmap. To view all the items we've prioritized for this quarter, please see the [Roadmap milestone](https://github.com/terraform-providers/terraform-provider-aws/milestone/138).
- 
+
 Where community sourced contributions exist we will work with the authors to review and merge their work. Where this does not exist we will create the resources and implementation ourselves.
- 
+
 From [May through July](docs/roadmaps/2020_May_to_July.md), we committed to adding support for WAFv2 and Lex. We are happy to report that WAFv2 support is now complete and we will be finishing support for Lex immediately following the release of v3.0.0. Additionally, we planned to refactor ACM and will include the redesigned resource as part of the 3.0.0 package. Lastly, we spent some time researching Default Tags and want to extend a thank you to all the folks that volunteered to assist. We’ve written a proposal for the feature that is being reviewed internally and we hope to include the functionality in the product in the future.
- 
-From August-October ‘20, we will be prioritizing the following areas of work:  
- 
+
+From August-October ‘20, we will be prioritizing the following areas of work:
+
 ## New Services
- 
+
 ### EventBridge
- 
+
 Issue: [#9330](https://github.com/terraform-providers/terraform-provider-aws/issues/9330)
- 
+
 _[Amazon EventBridge](https://aws.amazon.com/eventbridge/) is a serverless event bus that makes it easy to connect applications together using data from your own applications, integrated Software-as-a-Service (SaaS) applications, and AWS services. EventBridge delivers a stream of real-time data from event sources, such as Zendesk, Datadog, or Pagerduty, and routes that data to targets like AWS Lambda. You can set up routing rules to determine where to send your data to build application architectures that react in real time to all of your data sources._
- 
+
 As EventBridge exists as an addition to existing CloudWatch APIs we will perform a research phase to determine whether Terraform support should exist as separate resources, additions to existing ones, or a combination of the two.
- 
+
 ### EC2 Image Builder
- 
+
 Issue: [#11084](https://github.com/terraform-providers/terraform-provider-aws/issues/11084)
- 
+
 _[EC2 Image Builder](https://aws.amazon.com/image-builder/) simplifies the creation, maintenance, validation, sharing, and deployment of Linux or Windows Server images for use with Amazon EC2 and on-premises._
- 
-Support for EC2 Image Builder will include: 
- 
-New Resource(s): 
+
+Support for EC2 Image Builder will include:
+
+New Resource(s):
 - aws_imagebuilder_component
 - aws_imagebuilder_distribution_configuration
 - aws_imagebuilder_image
 - aws_imagebuilder_image_pipeline
 - aws_imagebuilder_image_recipe
 - aws_imagebuilder_infrastructure_configuration
- 
-New Data Source(s): 
+
+New Data Source(s):
 - aws_imagebuilder_image
- 
+
 ### AWS Lake Formation
- 
+
 Issue: [#9700](https://github.com/terraform-providers/terraform-provider-aws/issues/9700)
- 
+
 _[AWS Lake Formation](https://aws.amazon.com/lake-formation) is a service that makes it easy to set up a secure data lake in days. A data lake is a centralized, curated, and secured repository that stores all your data, both in its original form and prepared for analysis. A data lake enables you to break down data silos and combine different types of analytics to gain insights and guide better business decisions._
- 
-Support for AWS Lake Formation will include: 
- 
-New Resource(s): 
- 
+
+Support for AWS Lake Formation will include:
+
+New Resource(s):
+
 - aws_lakeformation_resource
 - aws_lakeformation_datalake_settings
 - aws_lakeformation_permissions
- 
+
 ### AWS Serverless Application Repository
- 
+
 Issue: [#3981](https://github.com/terraform-providers/terraform-provider-aws/issues/3981)
- 
+
 _The [AWS Serverless Application Repository](https://aws.amazon.com/serverless/serverlessrepo/) is a managed repository for serverless applications. It enables teams, organizations, and individual developers to store and share reusable applications, and easily assemble and deploy serverless architectures in powerful new ways. Using the Serverless Application Repository, you don't need to clone, build, package, or publish source code to AWS before deploying it. Instead, you can use pre-built applications from the Serverless Application Repository in your serverless architectures, helping you and your teams reduce duplicated work, ensure organizational best practices, and get to market faster. Integration with AWS Identity and Access Management (IAM) provides resource-level control of each application, enabling you to publicly share applications with everyone or privately share them with specific AWS accounts._
- 
-Support for AWS Serverless Application Repository will include: 
- 
+
+Support for AWS Serverless Application Repository will include:
+
 New Resource(s):
 - aws_serverlessrepository_stack
- 
-New Data Source(s): 
+
+New Data Source(s):
 - aws_serverlessrepository_application
- 
+
 ## Issues and Enhancements
- 
+
 The issues below have gained substantial support via our community. As a result, we want to highlight our commitment to addressing them.
- 
+
 - [#12690](https://github.com/terraform-providers/terraform-provider-aws/issues/12690) RDS Proxy Support
 - [#11281](https://github.com/terraform-providers/terraform-provider-aws/issues/11281) Home Directory Mappings Support for AWS Transfer User
 - [#384](https://github.com/terraform-providers/terraform-provider-aws/issues/384) Add support for CreateVPCAssociationAuthorization AWS API
 - [#6562](https://github.com/terraform-providers/terraform-provider-aws/issues/6562) Auto Scaling Plans (Dynamic/Predictive Auto Scaling Groups)
 - [#5549](https://github.com/terraform-providers/terraform-provider-aws/issues/5549) Terraform constantly updates resource policy on API Gateway
 - [#11569](https://github.com/terraform-providers/terraform-provider-aws/issues/11569) aws_transfer_server: support Elastic IPs
 - [#5286](https://github.com/terraform-providers/terraform-provider-aws/issues/5286) Point in time restore support for AWS RDS instances
- 
+
 ## United States Federal Focus
- 
+
 We have added extra engineering and product capacity to enable us to provide the same compatibility and coverage assurances in the GovCloud, C2S, and SC2S regions as we currently do for Commercial AWS regions. Our attention on C2S/SC2S environments should result in better outcomes in other similar air gapped environments. Initially, we will be focusing on GovCloud and users should expect improved experiences within that region in the coming months.
- 
+
 ## Technical Debt Theme
- 
+
 Each quarter we identify a technical debt theme for the team to focus on alongside new service additions, issue resolutions and enhancements. This quarter we are looking at spending time improving the reliability of our acceptance test framework. We have a number of flaky tests which add friction to the development cycle. Making these more consistent should improve the development experience for both contributors and maintainers.
- 
+
 ## Research Topics
- 
+
 Research topics include features, architectural changes, and ideas that we are pursuing in the longer term that may significantly impact the core user experience of the AWS provider. Research topics are discovery only and are not guaranteed to be included in a future release.
- 
+
 We are interested in your thoughts and feedback about the proposals below and encourage you to comment on the linked issues or schedule time with @maryelizbeth via the link on her GitHub profile to discuss.
- 
+
 ### API Calls/IAM Actions Per Terraform Resource (Minimum IAM)
- 
+
 Issue: [#9154](https://github.com/terraform-providers/terraform-provider-aws/issues/9154)
- 
-To address security concerns and best practices we are considering how Terraform could surface minimally viable IAM policies for taking actions on resources or executing a TF plan. This is in the early stages of research and we are particularly interested in whether or not this would be useful and the resources or services areas for which it is most valuable. 
- 
+
+To address security concerns and best practices we are considering how Terraform could surface minimally viable IAM policies for taking actions on resources or executing a TF plan. This is in the early stages of research and we are particularly interested in whether or not this would be useful and the resources or services areas for which it is most valuable.
+
 ### Lifecycle: Retain [Add 'retain' attribute to the Terraform lifecycle meta-parameter]
- 
+
 Issue: [#902](https://github.com/terraform-providers/terraform-provider-aws/issues/902)
- 
-Some resources (e.g. log groups) are intended to be created but never destroyed. Terraform currently does not have a lifecycle attribute for retaining such resources. We are curious as to whether or not retaining resources is a workflow that meets the needs of our community and if so, how and where we might make use of that in the AWS Provider. 
- 
+
+Some resources (e.g. log groups) are intended to be created but never destroyed. Terraform currently does not have a lifecycle attribute for retaining such resources. We are curious as to whether or not retaining resources is a workflow that meets the needs of our community and if so, how and where we might make use of that in the AWS Provider.
+
 ## Disclosures
- 
+
 The product-development initiatives in this document reflect HashiCorp's current plans and are subject to change and/or cancellation in HashiCorp's sole discretion.

docs/CORE_SERVICES.md

@@ -1,8 +1,8 @@
-# TF AWS Provider Core Services 
+# TF AWS Provider Core Services
 
-Core Services are AWS services we have identified as critical for a large majority of our users. Our goal is to continually increase the depth of coverage for these services. We will work to prioritize features and enhancements to these services in each weekly release, even if they are not necessarily highlighted in our quarterly roadmap. 
+Core Services are AWS services we have identified as critical for a large majority of our users. Our goal is to continually increase the depth of coverage for these services. We will work to prioritize features and enhancements to these services in each weekly release, even if they are not necessarily highlighted in our quarterly roadmap.
 
-The core services we have identified are: 
+The core services we have identified are:
 
 * EC2
 
@@ -24,4 +24,4 @@ The core services we have identified are:
 
 * Autoscaling (ASG)
 
-We'll continue to evaluate the selected services as our user base grows and changes. 
+We'll continue to evaluate the selected services as our user base grows and changes.

docs/FAQ.md

@@ -21,7 +21,7 @@ Unfortunately, due to the volume of issues and new pull requests we receive, we
 
 The number one factor we look at when deciding what issues to look at are your 👍 [reactions](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue/PR description as these can be [easily discovered](https://github.com/terraform-providers/terraform-provider-aws/issues?q=is%3Aopen+sort%3Areactions-%2B1-desc). Comments that further explain desired use cases or poor user experience are also heavily factored. The items with the most support are always on our radar, and we commit to keep the community updated on their status and potential timelines.
 
-We publish a [roadmap](../ROADMAP.md) every quarter which describes major themes or specific product areas of focus. 
+We publish a [roadmap](../ROADMAP.md) every quarter which describes major themes or specific product areas of focus.
 
 We also are investing time to improve the contributing experience by improving documentation, adding more linter coverage to ensure that incoming PR's can be in as good shape as possible. This will allow us to get through them quicker.
 

docs/MAINTAINING.md

@@ -5,7 +5,7 @@
 - [Pull Requests](#pull-requests)
     - [Pull Request Review Process](#pull-request-review-process)
         - [Dependency Updates](#dependency-updates)
-            - [Go Default Version Update](#go-default-version-update)        
+            - [Go Default Version Update](#go-default-version-update)
             - [AWS Go SDK Updates](#aws-go-sdk-updates)
             - [golangci-lint Updates](#golangci-lint-updates)
             - [Terraform Plugin SDK Updates](#terraform-plugin-sdk-updates)