Feat/make private api work#68
Open
globart wants to merge 3 commits into
Open
Conversation
Contributor
Author
|
Veronika Gnilitska (@gberenice) could you please check this? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
what
Introduced a new Terraform variable
ip_address_typeto allow explicit configuration of the network addressing scheme for the API infrastructure.Configured the variable by default to
dualstack, enabling native support for both IPv4 and IPv6 traffic routing.Implemented built-in Terraform validation to enforce strict compliance with valid AWS networking configurations (ipv4, ipv6, or dualstack), catching invalid inputs early during the plan phase.
why
Making the private API functional requires alignment with internal VPC routing architectures, especially when dealing with modern dual-stack environments or legacy IPv4-only networks.
Hardcoding the IP address type limits module reusability across different environments; exposing this parameter allows downstream deployments to adapt the API endpoints to local subnet restrictions.
Utilizing dualstack as the default ensures future-proof compatibility and seamless internal communication without breaking existing IPv4 workflows.
references