-
Notifications
You must be signed in to change notification settings - Fork 85
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
Add 'nat_type' in resource 'nsxt_policy_nat_rule' (INTERNAL, USER, DEFAULT) #1301
Comments
Thanks for the report @NonoCX In NSX API for NAT rules the category is controlled by the For instance setting a rule_priority < 1024 should result in the NAT rule being assigned to the INTERNAL category. If you did already try this and it's not working for you, we should treat this issue as a bug. |
This is fixed with #1480 - a new attribute |
Is your feature request related to a problem? Please describe.
With the API of NSX it can be possible to create NAT under 3 different categories/sections (INTERNAL, USER and DEFAULT).
https://dp-downloads.broadcom.com/api-content/apis/API_NTDCRA_001/3.2.1/html/api_includes/method_PatchPolicyNatRule.html
All NAT under INTERNAL are takes priority over USER categorie/section.
We need to create nat rules under INTERNAL to force SNAT of our customers' traffic when it join our shared services.
But when i use the resource
nsxt_policy_nat_rule
it is not possible to create nat rule under INTERNAL categorie/section. All rules are created under USER sectionDescribe the solution you'd like
Please, is it possible to add a feature for specify where the nat rule must be create under the categorie/section (INTERNAL, USER and DEFAULT) ?
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: