Open UVV-gh opened 5 months ago
Hey @UVV-gh ! Thanks for your interest in hawkBit!
Yes, indeed - the bahaviour you observe was planned to be like this.
Rejecting the action will preserve the WAIT_FOR_CONFIRMATION state. The reason for that is to give the user a chance to accept it at some point in time, if needed. If you want to dispose of the action you could cancel it, which will change the state to cancelled and the action will be closed.
... If you want to dispose of the action you could cancel it, which will change the state to cancelled and the action will be closed.
Thanks for the quick response. How can I cancel it from the device side? The cancellation API seems to expect a cancellation request from the server.
Which API are you using on the device side ? If it is DDI you can use the feedback channel for cancel actions which you can find in here https://eclipse.dev/hawkbit/apis/ddi_api/
That's the one that I use, yes. Could you please clarify how you see the workflow. What I have right now is the following:
@strailov any advice?
@strailov just checking if there's any more advices from your side.
Hey @UVV-gh Nope, I think your option is the feedback channel for cancel actions https://eclipse.dev/hawkbit/apis/ddi_api/
In other words - just report it cancelled from the device side after it was denied.
But that was exactly my question. If the action is not cancelled, is there actually a feedback channel for it?
Ah okay. Then what is wrong with the Feedback channel for the DeploymentBase action ? Since it is still running just report it cancelled there ?
According to your DDI API link above, that's not what neither DeploymentBase nor ConfirmationBase except as a response.
Hey there, I'm using confirmationBase endpoint to decide whether a rollout is suitable for the device. When the client reports "denied", the action is still there and is offered on the next poll interval. What are my options here to stop it from being offered further? I see the possibility to cancel it, but that doesn't look like a proper workflow.
My expected behavior would be that action is automatically closed when it's denied. Would that be a breaking change then?