Outbound NAT mapping protocol fix#66
Merged
jaredhendrickson13 merged 3 commits intomasterfrom Jan 29, 2021
Merged
Conversation
…otocol, updated unit test to test for this bug in the future
…otocol, updated unit test to test for this bug in the future
jaredhendrickson13
added
the
needs testing
jaredhendrickson13
removed
the
needs testing
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.
anyas a valid protocol for outbound NAT mappings and correctly translates the API value to the backend XML valuetests/test_api_v1_firewall_nat_outbound_mapping.pyto test for such a bug in the futureifvalue