GutoVeronezi commented on PR #7094:
URL: https://github.com/apache/cloudstack/pull/7094#issuecomment-1385309721

   @DaanHoogland @nvazquez @rohityadavcloud @weizhouapache 
   
   I redesigned the table `console_session` to store more data, based on the 
idea in https://github.com/apache/cloudstack/pull/7094#discussion_r1071235407. 
When generated via UI (ids 1, 2, and 3), the session is set as removed right 
away, as the UI redirects to the URL and consumes the session. When generated 
via API directly (id 4) , the session will not be set as removed until be 
consumed:
   
   
![image](https://user-images.githubusercontent.com/38945620/212887222-c4d588aa-e2df-4ee1-9f04-1476da964a8f.png)
   
   During the tests I did not notice a workflow to expire not used sessions. 
Will they be valid "forever" if not used? Or am I missing something? cc: 
@nvazquez 
   
   ---
   
   Regarding the `on cascade` clause, as the referenced entities are never 
deleted by ACS (they are only marked as removed), I do not see a reason to use 
it.
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to