Add CLIENTS and ACCESS_TOKENS to cache migration
Description
CAPL - Bug default text according to the team DoR (Definition of Ready)
01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM):
@Geny Isam Hamud Herrera
02 - PROBLEM (WHAT'S THE ISSUE?):
A routine was created to migrate the refresh_tokens records in redis on the 
03 - STEPS TO REPRODUCE (STEP (1...N), VIDEO, SCREENSHOTS, LOGS FOLDER, HEARTBEAT, ETC. – IF IS NOT POSSIBLE TO REPRODUCE EXPLAIN THE REASON):
04 - LINKS (ADD A LINK TO THE BUG OR TO THE TENANT):
05 - EXPECTED BEHAVIOR (LIST THE EXPECTED BEHAVIORS TO CONSIDER THIS BUG AS DONE):
We need to track if we change something in these entities(ex: change the type of field) in the last deployment that generated this bug. Maybe the solution is clean the caches to storage correct bytes again, but first is necessary to confirm what is changed
Activity
Details
Priority
High
Im going to put the card as done, since the card was not deployed because an inconsistency on the redis database. It is going to be solved on the card https://totvslabs.atlassian.net/browse/CAPL-5387
This issue was automatically transitioned to WAITING DEPLOY, as its linked QA regression issue has just reached WAITING DEPLOY status (PR was just merged into master branch in Github).
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to TESTED & MERGED, as its PR was just merged into develop branch in Github. PR Approved by douglascoimbra,Damore,douglascoimbra.
Github user douglascoimbra has just approved a PR (added as Shard Assignee in this Jira issue).
feat: https://totvslabs.atlassian.net/browse/CAPL-5326#icft=CAPL-5326 Added migration for ACCESS_TOKENS and CLIENTS cache
This issue was automatically transitioned to QA REVIEW, as its PR was just approved in Github.
@Glaucio Scheibel @Geny Isam Hamud Herrera @Gabriel DAmore Marciano Card revalidated by the QA team. It is pending the code review
This issue was automatically transitioned to QA REVIEW, as its PR was just approved in Github.
BEFORE SANDBOX REDEPLOY
AFTER REDEPLOY
@Glaucio Scheibel ,
@Jonathan Willian Moraes , @Gabriel DAmore Marciano , @Geny Isam Hamud Herrera
This issue was planned to be delivered until 2024-02-12. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-01-23, 2024-02-12
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.
feat: https://totvslabs.atlassian.net/browse/CAPL-5326#icft=CAPL-5326 Added migration for ACCESS_TOKENS and CLIENTS cache
This issue was automatically transitioned to IN PROGRESS, as its branch was just created in Github.
CAPL-5326-add-clients-and-access_tokens-to-cache-migration
@Janderson Fernandes Cardoso ,
@Glaucio Scheibel , @Gabriel DAmore Marciano , @Geny Isam Hamud Herrera
This issue was just linked to issue(s) https://totvslabs.atlassian.net/browse/CAPL-3821#icft=CAPL-3821, according to mention in the description field.
@Janderson Fernandes Cardoso ,
@Glaucio Scheibel , @Douglas Coimbra Lopes , @Gabriel DAmore Marciano , @Lucas Noetzold , @wilson.souza
This issue was planned to be delivered until 2024-01-23. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-01-23
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.