You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please give a one-sentence summary of the feature you would like to see.
We should be able to log commands in ddb as history.
Please give as many details as possible about the requirements for the feature.
We want maintainers to better see what commands were fired when to make it easier for debugging (instead of just looking at the logs, which may be a bit noisy at times). This may go nicely with a command, or be viewable from some admin console of some kind....
Please list any additional context.
Searching through the executed commands may be a future consideration.
The text was updated successfully, but these errors were encountered:
To make it even easier for debugging, we can attach a cmdID for each command execution so that we can search by cmdID instead of manually paging through the logs every time. Though this seems slightly unrelated to keeping track of the commands in ddb....
Please give a one-sentence summary of the feature you would like to see.
We should be able to log commands in ddb as history.
Please give as many details as possible about the requirements for the feature.
We want maintainers to better see what commands were fired when to make it easier for debugging (instead of just looking at the logs, which may be a bit noisy at times). This may go nicely with a command, or be viewable from some admin console of some kind....
Please list any additional context.
Searching through the executed commands may be a future consideration.
The text was updated successfully, but these errors were encountered: