Remove deleted tenant from Carol App deployed tenants list
Description
Issue Component(s) on Oct 24, 2023, 4:56:21 PM: CAROL_APP | INSTALATION
Person of contact
- @Bruno Furtado
Problem
In a development environment, where I have a dev app, there is the option to list all tenants where the app was deployed and I receive an error message informing a tenant was not found (the tenant was actually deleted a few months ago).
Steps to reproduce
1. Go to the dev tenant, dev app, tenants deployed list:
https://clockin.carol.ai/clockin/carol-ui/carol-app-dev/a85b7f1c39e24d87a1b6b6380b186138/tenants
More details
- Carol App Dev Tenant: clockin/clockin
- Carol App: clockinapp
- Deleted customer tenant:
a319b613e4544a839649cb9a1a077bcc
Expected behavior
- Remove the deleted tenant from tenants deployed list of the app.
- Make there is no other wrong IDs (in case true, delete also).
- When removing a tenant or org, ensure this problem does not happening.
As stated on the Instructions of this card, the cleasing of invalid tenants will be done by SRE team. This card will be focused on not throwing the exception if a tenant is invalid inside the list of tenants to be shown.
Activity
Show:
Details
Priority
HighestAssignee
Rodrigo Bechtold
Reporter
MARCOS STUMPF
Labels
CAROL_BACKLOG_REVIEWPLANNEDPLATFORM_LEADERSHIP_REVIEWREADYREVIEWED
Due Date
4 March 2024
Fix versions
CAPL_4.00
Components
CAROL_APP | INSTALATION
Created
21 December 2023, 14:41
Updated
19 April 2024, 10:16
More fields
Created: 21 December 2023, 18:41
Updated:
19 April 2024, 15:16
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa 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 REGRESSION, as its PR was just merged into qa branch in Github.
@MARCOS STUMPF ,
@Gabriel DAmore Marciano , @Rodrigo Bechtold , @André Pereira de Oliveira , @Douglas Coimbra Lopes , @Renan Schroeder
This issue was planned to be delivered until 2024-03-04. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-02-12, 2024-03-04
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
This issue was automatically transitioned to TESTED & MERGED, as its PR was just merged into develop branch in Github. PR Approved by rfschroeder,douglascoimbra.
Github user douglascoimbra has just approved a PR (added as Shard Assignee in this Jira issue).
fix: - Handle tenantApp of a deleted tenant
This issue was automatically transitioned to QA REVIEW, as its PR was just approved in Github.
Github user rodrigo-bechtold has just commited and issue was sent back to the REVIEW column.
Github user douglascoimbra has just approved a PR (added as Shard Assignee in this Jira issue).
fix: - Handle tenantApp of a deleted tenant
USING AN INVALID TENANT ID IN ORDER TO REPLICATE ANOTHER APP WITH THE SAME NAME ON ES
NO ERRORS DETECTED FROM INSTALLED APPS REQUEST
BE ANF FE PERSPECTIVE
UNIFIED OK ALSO
Cenario encontrado no card .
:white_check_mark: Update: Topico resolvido. UUID Format corrigdo para o teste do appName
• Apos efetuar os steps do card, ao acessar a tela Tenants Deployed, uma mensagem de erro eh exibida ao usuario, diferente do reportado.
• Verificando se na develop tbm ocorre :loading:
Edited on Slack - platform-internal - Douglas Coimbra Lopes
:rotating_light: Cenario encontrado no card .
• Apos efetuar os steps do card, ao acessar a tela Tenants Deployed, uma mensagem de erro eh exibida ao usuario, diferente do reportado.
• Verificando se na develop tbm ocorre :loading:
Sent by Slack - platform-internal - Douglas Coimbra Lopes
This issue was automatically transitioned to QA REVIEW, as its PR was just approved in Github.
This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.
fix: - Handle tenantApp of a deleted tenant
@MARCOS STUMPF ,
@Jonathan Willian Moraes , @André Pereira de Oliveira
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-02-12
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.