-
Notifications
You must be signed in to change notification settings - Fork 13
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
Delete instance api #1037
Delete instance api #1037
Conversation
59f5069
to
e937c55
Compare
77f3e5c
to
eaa1873
Compare
service:delete deletes the service even if an instance is running which is the opposite behavior in the proposal |
} | ||
|
||
message DeleteInstanceResponse { | ||
string hash = 1; // Instance hash |
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.
why return instance hash in response if it was sent in the request
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.
I don't mind much about that, I can remove but the idea is that when we delete a resource we have the id of the resource delete in order to be able to have a full asynchrony application that can on one side send the request and on the other side just receive the result and know how to update a local store or anything.
But again I'm happy to delete it if needed
…esg-foundation/core into feature/instance-delete-server
f65a512
to
3b77b73
Compare
dependency: #1036