Fix for handling broadcom DNX ASIC to have ipv4 and ipv6 ACL rules in separate tables. #2178
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 I did
Fix for handling broadcom DNX ASIC to have ipv4 and ipv6 ACL rules in separate tables.
Related PR : sonic-net/sonic-buildimage#10235
Why I did it
Broadcom DNX ASIC need to have ipv4 and ipv6 ACL rules in separate tables.
How I verified it
Verified the SWSS_VARS is updated and sub_platfom populated with 'broadcom-dnx'
Details if related