You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: ROADMAP.md
+47-75
Original file line number
Diff line number
Diff line change
@@ -1,30 +1,29 @@
1
-
# Roadmap: August 2021 - October 2021
1
+
# Roadmap: November 2021 - January 2022
2
2
3
3
Every few months, the team will highlight areas of focus for our work and upcoming research.
4
4
5
-
We select items for inclusion in the roadmap from the Top 10 Community Issues, [Core Services](docs/contributing/core-services.md), and internal priorities. Where community sourced contributions exist we will work with the authors to review and merge their work. Where this does not exist or the original contributors are not available we will create the resources and implementation ourselves.
5
+
We select items for inclusion in the roadmap from the Top Community Issues, [Core Services](docs/contributing/core-services.md), and internal priorities. Where community sourced contributions exist we will work with the authors to review and merge their work. Where this does not exist or the original contributors are not available we will create the resources and implementation ourselves.
6
6
7
7
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/hashicorp/terraform-provider-aws/milestone/138).
8
8
9
9
This roadmap does not describe all the work that will be included within this timeframe, but it does describe our focus. We will include other work as events occur .
10
10
11
-
In the period spanning May to July 2021 539 Pull Requests were opened in the provider and 449 were merged, adding support for:
11
+
In the period spanning August to October 2021, 573 Pull Requests were opened in the provider and 465 were merged, adding support for:
12
12
13
-
- Amazon Timestream
14
-
- AWS AppConfig
15
-
- AWS Amplify
16
-
- AWS Service Catalog
17
-
- AWS Elasticsearch Native SAML for Kibana
18
-
- Amazon Macie 2
19
-
- Delegated Administrators for Organisations
20
-
- Predictive Autoscaling
21
-
- Amazon EKS OIDC
22
-
- AWS Transfer Family support for Amazon Elastic File System
23
-
- Amazon Kinesis Data Streams for Amazon DynamoDB
13
+
- Amazon Chime
14
+
- Amazon Connect
15
+
- Amazon AppStream 2.0
16
+
- Route 53 Recovery Control
17
+
- Graviton2 support for Lambda
18
+
- S3 Replication Time Control
24
19
25
-
Among many other enhancements, bug fixes and resolutions to technical debt items.
20
+
We also launched a fully generated provider, the AWS Cloud Control (AWSCC) provider for Terraform. The AWSCC provider is currently in Technical Preview. Please check it out and let us know what you think.
26
21
27
-
From August-October ‘21, we will be prioritizing the following areas of work:
22
+
-[HashiCorp Blog Announcement](https://www.hashicorp.com/blog/announcing-terraform-aws-cloud-control-provider-tech-preview)
_Amazon QuickSight is a scalable, serverless, embeddable, machine learning-powered business intelligence (BI) service built for the cloud. QuickSight lets you easily create and publish interactive BI dashboards that include Machine Learning-powered insights. QuickSight dashboards can be accessed from any device, and seamlessly embedded into your applications, portals, and websites._
_Amazon AppStream 2.0 is a fully managed non-persistent desktop and application virtualization service that allows your users to securely access the data, applications, and resources they need, anywhere, anytime, from any supported device. With AppStream 2.0, you can easily scale your applications and desktops to any number of users across the globe without acquiring, provisioning, and operating hardware or infrastructure. AppStream 2.0 is built on AWS, so you benefit from a data center and network architecture designed for the most security-sensitive organizations. Each end user has a fluid and responsive experience because your applications run on virtual machines optimized for specific use cases and each streaming sessions automatically adjusts to network conditions._
_Amazon Connect is an easy to use omnichannel cloud contact center that helps you provide superior customer service at a lower cost. Designed from the ground up to be omnichannel, Amazon Connect provides a seamless experience across voice and chat for your customers and agents. This includes one set of tools for skills-based routing, task management, powerful real-time and historical analytics, and intuitive management tools – all with pay-as-you-go pricing, which means Amazon Connect simplifies contact center operations, improves agent efficiency, and lowers costs. You can set up a contact center in minutes that can scale to support millions of customers from the office or as a virtual contact center._
75
-
76
-
Support for Amazon Connect will include:
77
-
78
-
New Resource(s):
79
-
- aws_connect_instance
80
-
- aws_connect_contact_flow
81
-
- aws_connect_bot_association
82
-
- aws_connect_lex_bot_association
83
-
- aws_connect_lambda_function_association
84
-
85
-
New Data Source(s):
86
-
- aws_connect_instance
87
-
- aws_connect_contact_flow
88
-
- aws_connect_bot_association
89
-
- aws_connect_lex_bot_association
90
-
- aws_connect_lambda_function_association
91
-
92
38
## Enhancements to Existing Services
93
-
-[Support for KMS Multi-Region Keys](https://github.com/hashicorp/terraform-provider-aws/issues/19896)
94
-
-[S3 Replication Time Control](https://github.com/hashicorp/terraform-provider-aws/issues/10974)
95
-
-[New Data Source: aws_iam_roles](https://github.com/hashicorp/terraform-provider-aws/issues/14470)
96
-
97
-
## Project Restructure: Service Level Packages
98
39
99
-
The scale of the provider (now 1000 resources/datasources) has led to its existing package structure being difficult to work with and maintain. This quarter we are going to perform a large refactor of the codebase, to align on a single go package per AWS service. More details can be found in the encompassing issue [#20431](https://github.com/hashicorp/terraform-provider-aws/issues/20431)
40
+
-[Support for Managing Amazon CloudSearch Domains](https://github.com/hashicorp/terraform-provider-aws/issues/7833)
41
+
-[aws_config_remediation_configuration: No support for "automatic" remediation](https://github.com/hashicorp/terraform-provider-aws/issues/15491)
-[Order is lost for data aws_iam_policy_document when applied to S3 buckets, iam roles, kms keys](https://github.com/hashicorp/terraform-provider-aws/issues/11801)
69
+
-[aws_ecs_cluster with capacity_providers cannot be destroyed](https://github.com/hashicorp/terraform-provider-aws/issues/11409)
70
+
-[Support for Account Settings Flags](https://github.com/hashicorp/terraform-provider-aws/issues/10168)
71
+
-[Execute AWS Lambda Only Once](https://github.com/hashicorp/terraform-provider-aws/issues/4746)
Every few months, the team will highlight areas of focus for our work and upcoming research.
4
+
5
+
We select items for inclusion in the roadmap from the Top 10 Community Issues, [Core Services](docs/contributing/core-services.md), and internal priorities. Where community sourced contributions exist we will work with the authors to review and merge their work. Where this does not exist or the original contributors are not available we will create the resources and implementation ourselves.
6
+
7
+
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/hashicorp/terraform-provider-aws/milestone/138).
8
+
9
+
This roadmap does not describe all the work that will be included within this timeframe, but it does describe our focus. We will include other work as events occur .
10
+
11
+
In the period spanning May to July 2021 539 Pull Requests were opened in the provider and 449 were merged, adding support for:
12
+
13
+
- Amazon Timestream
14
+
- AWS AppConfig
15
+
- AWS Amplify
16
+
- AWS Service Catalog
17
+
- AWS Elasticsearch Native SAML for Kibana
18
+
- Amazon Macie 2
19
+
- Delegated Administrators for Organisations
20
+
- Predictive Autoscaling
21
+
- Amazon EKS OIDC
22
+
- AWS Transfer Family support for Amazon Elastic File System
23
+
- Amazon Kinesis Data Streams for Amazon DynamoDB
24
+
25
+
Among many other enhancements, bug fixes and resolutions to technical debt items.
26
+
27
+
From August-October ‘21, we will be prioritizing the following areas of work:
The next major release of the provider will include the adoption of the AWS Go SDK v2.0 as well as a refactor of one of our oldest and most used resources: S3.
34
+
35
+
There will also be the usual deprecations and sometimes breaking changes to existing resources which are necessary to maintain consistency of behavior across resources. Our goal is to focus on standardization to reduce technical debt and lay a strong foundation for future enhancement initiatives within the provider.
36
+
37
+
For details of the changes in full please refer to #20433. We would love to hear your feedback.
_Amazon QuickSight is a scalable, serverless, embeddable, machine learning-powered business intelligence (BI) service built for the cloud. QuickSight lets you easily create and publish interactive BI dashboards that include Machine Learning-powered insights. QuickSight dashboards can be accessed from any device, and seamlessly embedded into your applications, portals, and websites._
_Amazon AppStream 2.0 is a fully managed non-persistent desktop and application virtualization service that allows your users to securely access the data, applications, and resources they need, anywhere, anytime, from any supported device. With AppStream 2.0, you can easily scale your applications and desktops to any number of users across the globe without acquiring, provisioning, and operating hardware or infrastructure. AppStream 2.0 is built on AWS, so you benefit from a data center and network architecture designed for the most security-sensitive organizations. Each end user has a fluid and responsive experience because your applications run on virtual machines optimized for specific use cases and each streaming sessions automatically adjusts to network conditions._
_Amazon Connect is an easy to use omnichannel cloud contact center that helps you provide superior customer service at a lower cost. Designed from the ground up to be omnichannel, Amazon Connect provides a seamless experience across voice and chat for your customers and agents. This includes one set of tools for skills-based routing, task management, powerful real-time and historical analytics, and intuitive management tools – all with pay-as-you-go pricing, which means Amazon Connect simplifies contact center operations, improves agent efficiency, and lowers costs. You can set up a contact center in minutes that can scale to support millions of customers from the office or as a virtual contact center._
77
+
78
+
Support for Amazon Connect will include:
79
+
80
+
New Resource(s):
81
+
82
+
- aws_connect_instance
83
+
- aws_connect_contact_flow
84
+
- aws_connect_bot_association
85
+
- aws_connect_lex_bot_association
86
+
- aws_connect_lambda_function_association
87
+
88
+
New Data Source(s):
89
+
90
+
- aws_connect_instance
91
+
- aws_connect_contact_flow
92
+
- aws_connect_bot_association
93
+
- aws_connect_lex_bot_association
94
+
- aws_connect_lambda_function_association
95
+
96
+
## Enhancements to Existing Services
97
+
98
+
-[Support for KMS Multi-Region Keys](https://github.com/hashicorp/terraform-provider-aws/issues/19896)
99
+
-[S3 Replication Time Control](https://github.com/hashicorp/terraform-provider-aws/issues/10974)
100
+
-[New Data Source: aws_iam_roles](https://github.com/hashicorp/terraform-provider-aws/issues/14470)
101
+
102
+
## Project Restructure: Service Level Packages
103
+
104
+
The scale of the provider (now 1000 resources/datasources) has led to its existing package structure being difficult to work with and maintain. This quarter we are going to perform a large refactor of the codebase, to align on a single go package per AWS service. More details can be found in the encompassing issue [#20431](https://github.com/hashicorp/terraform-provider-aws/issues/20431)
105
+
106
+
## Research Topics
107
+
108
+
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.
109
+
110
+
### Scaffolding for new resources, datasources and associated tests
111
+
112
+
Adding resources, datasources and test files to the provider is a repetitive task which should be automated to ensure consistency and speed up contributor and maintainer workflow. A simple cli tool should be able to generate these files in place, and ensure that any code reference additions required (ie adding to `provider.go`) are performed as part of the process.
113
+
114
+
## Disclosures
115
+
116
+
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.
0 commit comments