-
Notifications
You must be signed in to change notification settings - Fork 16
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
Added support for delete meter configuration #381
Conversation
Signed-off-by: bharticemk <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I've made a couple of minor suggestions.
@@ -78,6 +78,7 @@ for P4Runtime switches: | |||
add-meter-config SWITCH MTR_TBL MTR_FLOW add packet mod meter config table entry | |||
get-packet-mod-meter SWITCH MTR_TBL MTR_FLOW gets packet mod meter table entry | |||
get-direct-pkt-mod-meter SWITCH MTR_TBL MTR_FLOW gets direct packet mod meter table entry | |||
del-meter-config SWITCH MTR_TBL MTR_FLOW delete packet mod meter config table entry |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You might want to consider alphabetizing the meter commands
ce = entity.meter_entry | ||
|
||
if ce is None: | ||
raise Exception("Cannot find meter_entry field in entity") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't something like "No meter_entry field in entity" or "Entity does not specify meter_entry field" be more accurate? You're not exactly searching for it.
No description provided.