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
{{ message }}
This repository has been archived by the owner on May 26, 2023. It is now read-only.
I'd like to see some discussion as whether or not the inclusion of the 'db purge' command is appropriate for edgex-cli. Most, if not all of the other commands exercise EdgeX's REST APIs.
I see that the command implements a "do you really want to do this check", which is great, however I would feel more comfortable with pointing someone to the actual db tools (e.g. redis-cli).
Maybe this could be discussed at an upcoming Core WG meeting?
Version: v1.0.0-dev.28
The text was updated successfully, but these errors were encountered:
The initial idea was to keep the client unaware of the underlying implementation - unaware of what is the used database and still test most of the Delete exported apis . But better is to have a discussion about it.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'd like to see some discussion as whether or not the inclusion of the 'db purge' command is appropriate for edgex-cli. Most, if not all of the other commands exercise EdgeX's REST APIs.
I see that the command implements a "do you really want to do this check", which is great, however I would feel more comfortable with pointing someone to the actual db tools (e.g. redis-cli).
Maybe this could be discussed at an upcoming Core WG meeting?
Version: v1.0.0-dev.28
The text was updated successfully, but these errors were encountered: