-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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/vpc_endpoint: fix private_dns_only_for_inbound_resolver_endpoint #32021
r/vpc_endpoint: fix private_dns_only_for_inbound_resolver_endpoint #32021
Conversation
This field was always set to True or nil, and could not be set to False.
Community NoteVoting for Prioritization
For Submitters
|
|
Sorry for letting this go stale, will have an update in the next day or so. |
@FabianPonce Thanks for the contribution 🎉 👏. The functionality has been implemented in #32355. |
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. |
Description
This PR is a follow-on from #31873 , which seems to have a defect. In order to create a VPC Endpoint for S3 in Interface mode, the field
private_dns_only_for_inbound_resolver_endpoint
MUST be set tofalse
.In the previous PR, the value was only sent when
true
, otherwise asnil
. AWS interprets thenil
option the same as if it were set totrue
, which is odd.In any case, it was impossible to set this value to
false
.In the case of this value being set to
false
, the test should have no dependency on a VPC Endpoint of GATEWAY type. The test passed in the previous PR because the gateway was created and the value was interpreted astrue
.In the case of this value being set to
true
, this test continues to have a dependency on the VPC Endpoint of GATEWAY type.Relations
Closes #30041.
Relates #31873.
Output from Acceptance Testing