Skip to content

resource/aws_redshift_cluster: Update default value of encrypted to true to match AWS default #42631

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

Open
wants to merge 29 commits into
base: release/6.0.0-beta
Choose a base branch
from

Conversation

gdavison
Copy link
Contributor

@gdavison gdavison commented May 15, 2025

Rollback Plan

If a change needs to be reverted, we will publish an updated version of the provider.

Changes to Security Controls

None

Description

AWS defaults to encryption at rest, but the default value of encrypted is false. This PR updates the default value to true. It also fixes a bug where encryption cannot be set to false on creation.

Additionally removes unneeded availability zone restrictions on acceptance tests.

Relations

Closes #42598

References

Output from Acceptance Testing

% make testacc TESTS=TestAccXXX PKG=ec2

...

Copy link

Community Guidelines

This comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

  • Please vote on this Pull Request by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
  • Please see our prioritization guide for additional information on how the maintainers handle prioritization.
  • Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Pull Request and do not help prioritize the request.

Pull Request Authors

  • Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
  • Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

Copy link

github-actions bot commented May 15, 2025

✅ Thank you for correcting the previously detected issues! The maintainers appreciate your efforts to make the review process as smooth as possible.

@github-actions github-actions bot added documentation Introduces or discusses updates to documentation. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure. service/redshift Issues and PRs that pertain to the redshift service. prioritized Part of the maintainer teams immediate focus. To be addressed within the current quarter. size/XL Managed by automation to categorize the size of a PR. labels May 15, 2025
@github-actions github-actions bot added service/dms Issues and PRs that pertain to the dms service. service/redshiftdata Issues and PRs that pertain to the redshiftdata service. service/pipes Issues and PRs that pertain to the pipes service. labels May 15, 2025
@gdavison gdavison added this to the v6.0.0-beta2 milestone May 15, 2025
@gdavison gdavison marked this pull request as ready for review May 15, 2025 19:11
@gdavison gdavison requested a review from a team as a code owner May 15, 2025 19:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Introduces or discusses updates to documentation. prioritized Part of the maintainer teams immediate focus. To be addressed within the current quarter. service/dms Issues and PRs that pertain to the dms service. service/pipes Issues and PRs that pertain to the pipes service. service/redshift Issues and PRs that pertain to the redshift service. service/redshiftdata Issues and PRs that pertain to the redshiftdata service. size/XL Managed by automation to categorize the size of a PR. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant