allow restriction of destination ip address #53
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.
See #49
We no longer throw an error if we connect to IP address while a
ALLOWED_DEST_FQDNis set, instead we check that the destination IP address matches the pattern. This is the simplest possible change that allows users to restrict which IP addresses can be connected to. A more elaborate change would be to introduce a new environment variable that reflects that both IP addresses and domain names can be restricted. I don't mind either solution.