v2.69.1 proposal, ensure AWS terraform provider v2.70.0 compatibility #587
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
service_type
parameter.Motivation and Context
After this week's release of privatelink for s3, the fixes implemented in v2.69.0 and v2.70.0 don't mitigate errors when using the AWS Terraform provider
v2.X.X
Addresses:
Breaking Changes
This is a proposed patch release for
v2.69.
which did not resolve the original issue.How Has This Been Tested?
This was tested by creating vpc endpoint services with AWS Terraform Provider
2.70.0
and that no error occurred./cc @tbugfinder