Skip to content
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

r/redis_cache: case-insensitively parsing the Subnet ID to normalise it #14108

Merged
merged 3 commits into from
Nov 10, 2021

Conversation

tombuildsstuff
Copy link
Contributor

This PR fixes #13838 by parsing the subnet_id field case-insensitively rather than case-sensitively.

This also applies this change to the Data Source so these values are consistently normalised (and ensures that the shardCount field always has the default value, which was spotted in passing)

Supersedes the work done by @damienpontifex in #13870

This fixes #13838 by working around an incorrectly cased ID in the response
This fixes #13838 for the data source too, by normalizing the SubnetId here
Copy link
Contributor

@koikonom koikonom left a comment

Choose a reason for hiding this comment

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

LGTM

@tombuildsstuff
Copy link
Contributor Author

Tests pass:

Screenshot 2021-11-09 at 17 10 06

@tombuildsstuff tombuildsstuff merged commit 7a38e77 into main Nov 10, 2021
@tombuildsstuff tombuildsstuff deleted the b/13838-redis-parse-subnet-insensitively branch November 10, 2021 07:07
tombuildsstuff added a commit that referenced this pull request Nov 10, 2021
@github-actions
Copy link

This functionality has been released in v2.85.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

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 contributions.
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 Dec 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ID was missing the virtualNetworks when importing redis resource
2 participants