IPV4_ONLY and IPV6_ONLY environment control added #235
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:
Related issue (if applicable): refs #211
Added 2 new environment variables that allow the exclusive enforcing of an IPv4 or IPv6 environment only.
IPV4_ONLY: Eliminate any IPv6 configuration in place to run n an exclusive IPv4 modeIPV6_ONLY: Eliminate any IPv4 configuration in place to run in an exclusive IPv6 modeFor obvious reasons, it's ambigious to set both environment variables, so if this is detected, nothing is updated/changed within the docker environment.
E.g.:
In the example, i set the
IPV4_ONLYtoy, but really it doesn't matter what you equate the environment variable too. As long as it has been defined, it will trigger the enforcing code of the respeced IP version.Checklist
flake8)