Skip to content

feat!: Add support for data tiering attribute, bump minimum supported versions of Terraform and AWS provider #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Aug 11, 2023

Conversation

typat
Copy link
Contributor

@typat typat commented Aug 10, 2023

Description

Without the ability to set the data tiering parameter during cluster creation, data tiering node types are not able to be used. The data tiering attribute is supported by the AWS provider since v4.42.0

VPC version was updated to 4 to get validate passing due to enable_classiclink being removed in AWS Provider 5.0.0.

Motivation and Context

This change allows the use of data tiering node groups and supports hashicorp/terraform-provider-aws#28022.

Breaking Changes

Yes, lots of breaking changes due to major version increase in AWS provider.

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have executed pre-commit run -a on my pull request

@typat typat changed the title Add support for data tiering attribute feat: Add support for data tiering attribute Aug 10, 2023
versions.tf Outdated
@@ -4,7 +4,7 @@ terraform {
required_providers {
aws = {
source = "hashicorp/aws"
version = ">= 3.71"
version = ">= 4.42.0"
Copy link
Member

@bryantbiggs bryantbiggs Aug 10, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this is now a breaking change, lets just go all the way up to v5.0 of the AWS provider

Also, lets move the min required version of Terraform up to 1.0

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sounds good!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah missed your second comment

node_type = "db.r6gd.xlarge"
num_shards = 2
num_replicas_per_shard = 2
data_tiering = true
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can add this to the existing example - no need for a whole new example just for this

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

perfect. i debated this but wasnt sure

@bryantbiggs bryantbiggs changed the title feat: Add support for data tiering attribute feat!: Add support for data tiering attribute, bump minimum supported versions of Terraform and AWS provider Aug 11, 2023
Copy link
Member

@bryantbiggs bryantbiggs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@bryantbiggs bryantbiggs merged commit 1c94464 into terraform-aws-modules:master Aug 11, 2023
antonbabenko pushed a commit that referenced this pull request Aug 11, 2023
## [2.0.0](v1.1.2...v2.0.0) (2023-08-11)

### ⚠ BREAKING CHANGES

* Add support for data tiering attribute, bump minimum supported versions of Terraform and AWS provider (#5)

### Features

* Add support for data tiering attribute, bump minimum supported versions of Terraform and AWS provider ([#5](#5)) ([1c94464](1c94464))
@antonbabenko
Copy link
Member

This PR is included in version 2.0.0 🎉

@typat
Copy link
Contributor Author

typat commented Aug 11, 2023

thanks for the quick feedback!

Copy link

github-actions bot commented Mar 7, 2024

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants