Replies: 1 comment
-
This is a good idea, but implementing this as a part of trice will overburden the tool from my current point of view. At least there is then a configuration needed. How you will protect the config file? For your use case maybe some different batch files are sufficient. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Different users would be able to see different levels of information.
For example:
trice log -port COM13 -ts "ms" -password DevPassword
access to every trice
trice log -port COM13 -ts "ms" -password QAPassword
access to generic information with some data, let's say that it's the same as "-pick info -pick error"
trice log -port COM13 -ts "ms" -password ProductionPassword
access to specific information, let's say that it's the same as "-pick msg"
The difference between this and "-pick" would be that the production couldn't change the flag and have access to the whole information.
Beta Was this translation helpful? Give feedback.
All reactions