@Cindy de Araujo Soares Moore ,
@André Pereira de Oliveira , @Douglas Coimbra Lopes , @MARCOS STUMPF

The JIRA TOTVS issues https://jiraproducao.totvs.com.br/browse/DLABSCAPL-3624 was just closed because it was waiting customer more than 10 days. This JIRA LABS issue was also transitioned to done.

@Cindy de Araujo Soares Moore ,
@MARCOS STUMPF , @André Pereira de Oliveira ,

You have just moved the JIRA TOTVS issue https://jiraproducao.totvs.com.br/browse/DLABSCAPL-3624 to the Customer responsability.

:red_circle: HEADS UP: Issue Creator on JIRA TOTVS BRAZIL is currently INACTIVE (maybe on vacation).

#customer

Prezado cliente, informamos que a issue foi liberada em produção há 8 dias atrás.

Solicitamos validar a solução para que possamos proceder com o encerramento do card em caso de sucesso.

Obrigado.

@Cindy de Araujo Soares Moore ,
@André Pereira de Oliveira , @Douglas Coimbra Lopes , @Gabriel DAmore Marciano , @Geny Isam Hamud Herrera

Heads Up!
Changed Issue field(s) URL Documento Técnico on Jira Brazil Issue.

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).

The first AC of the card is not going to be covered and it is split into two new cards:
1-
2-

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 genyherrera,douglascoimbra.

Github user douglascoimbra has just approved a PR (added as Shard Assignee in this Jira issue).

fix: CarolApp installation triggered by Carol Admin causing Staging Table with Inactive status

This issue was automatically transitioned to QA REVIEW, as its PR was just approved in Github.

@Cindy de Araujo Soares Moore ,
@André Pereira de Oliveira , @Douglas Coimbra Lopes

Comment sent to JIRA TOTVS Brazil - https://jiraproducao.totvs.com.br/browse/DLABSCAPL-3624:

Informamos que esta issue foi incluída em uma sprint com previsão de entrega até 2024-01-22 (podendo ocorrer retorno antes). Não é necessário retornar esta interação, caso não tenha dúvidas. Qualquer alteração de planejamento será novamente notificada nesta issue.

Atenciosamente,
Equipe TOTVS LABS.

@Cindy de Araujo Soares Moore ,
@Geny Isam Hamud Herrera , @André Pereira de Oliveira , @Douglas Coimbra Lopes

This issue was planned to be delivered until 2024-01-22. You can check that by consulting the issue in the Due Date field.

Dates already planned for this issue: 2024-01-22, 2023-12-11, 2024-01-02

If External Issue Link field is filled, customer was also informed on JIRA TOTVS.

@André Pereira de Oliveira The card has been validated by the QA team. It is pending only the code review. cc @Gabriel DAmore Marciano @Geny Isam Hamud Herrera

This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.

fix: CarolApp installation triggered by Carol Admin causing Staging Table with Inactive status

SECOND TEST

UPDATE CAROL APP

:rotating_light: Bom dia. Cenario identificado no card .
• Carol Admin via impersonation nao consegue efetuar update no parametro `mdmBigQuerySynchronizationStatus`. Ao passar o parametro junto ao schema update, eh apresentado uma msg de erro
• CURL disponivel no card

Sent by Slack - platform-internal - Douglas Coimbra Lopes

@Cindy de Araujo Soares Moore ,
@André Pereira de Oliveira , @Douglas Coimbra Lopes

Heads Up!
Changed Issue field(s) status, resolution on Jira Brazil Issue.

@Cindy de Araujo Soares Moore ,
@André Pereira de Oliveira , @Douglas Coimbra Lopes

The JIRA TOTVS issues https://jiraproducao.totvs.com.br/browse/DLABSCAPL-3624 was just closed because it was waiting customer more than 10 days. This JIRA LABS issue was also transitioned to done.

@Douglas Coimbra Lopes

When I checked the status was SYNCHRONIZED. I think it was a slow integration between the platform and data.

Tuesday, I’d like to retry this test.

@André Pereira de Oliveira TEST FAILED

• When the Carol app is installed by the Carol admin, the staging schema mdmBigQuerySynchronizationStatus parameter is still as INACTIVE. Please check below the steps made

• app installed: myapp

• tenant installed:

• staging table: product

INSTALLING CAROL APP AS CAROL ADMIN (FIRST VERSION)

CAROL ADMIN IMPERSONATING AND MANIPULATING BIG QUERY PARAMETERS FOR STAGING

• NOW ALLOWING TENATADMIN/ORGADMIN TO PERFORM THIS ACTION

@Cindy de Araujo Soares Moore ,
@Ieda Beatriz Closa Brasil , @Renan Schroeder ,

You have just moved the JIRA TOTVS issue https://jiraproducao.totvs.com.br/browse/DLABSCAPL-3624 to the Customer responsability.

#customer

Léo,

Este tema ainda tem alguma pendência ou podemos encerrá-lo?

Obrigada.

@Renan Schroeder bom dia.

Como está a situação deste card? Podemos concluir para o cliente ou ainda tem algo a ser tratado?

@Cindy de Araujo Soares Moore ,
@Gabriel DAmore Marciano , @Renan Schroeder ,

Flag was removed since you have just transitioned the issue status/column.

@Cindy de Araujo Soares Moore ,
@Renan Schroeder ,

Comment sent to JIRA TOTVS Brazil - https://jiraproducao.totvs.com.br/browse/DLABSCAPL-3624:

Informamos que esta issue foi incluída em uma sprint com previsão de entrega até 2024-01-01 (podendo ocorrer retorno antes). Não é necessário retornar esta interação, caso não tenha dúvidas. Qualquer alteração de planejamento será novamente notificada nesta issue.

Atenciosamente,
Equipe TOTVS LABS.

@Cindy de Araujo Soares Moore ,
@Pedro Buzzi , @Renan Schroeder ,

This issue was planned to be delivered until 2024-01-01. You can check that by consulting the issue in the Due Date field.

Dates already planned for this issue: 2023-12-11, 2024-01-01

If External Issue Link field is filled, customer was also informed on JIRA TOTVS.

Flag added

This card is now hard stopped because of the pair programming @Renan Schroeder will do with @Emerson Venancio since this is his last week

Additional details asked by @Renan Schroeder,

I was using my Carol Admin user credentials and using 'overriddentenantid': tenant['mdmId'] in the request I could use scale the executions and not have to access each tenant individually.

A sample of the code:

load_dotenv()

carol = pycarol.Carol(auth=pycarol.PwdAuth(os.environ.get("CAROLUSER"), os.environ.get("CAROLPWD")), organization='global', domain='admin')

if args.get('tenantid'):

    tenant = carol.call_api(f'v3/admin/tenants/{args.get("tenantid")}', 'GET')

elif args.get('tenant'):

    tenant = carol.call_api(f'v3/tenants/domain/{args.get("tenant")}', 'GET')

else:

    raise Exception("Tenant not found!!! Use --tenant or --tenantid")

subscribe = carol.call_api(f'v1/tenantApps/subscribe/carolApps/{app["mdmId"]}', 'POST', extra_headers={'overriddentenantid': tenant['mdmId']})

update = carol.call_api(f'v1/tenantApps/{subscribe["mdmId"]}/install?publish=true', 'POST', extra_headers={'overriddentenantid': tenant['mdmId']})

Where:

tenant['mdmId'] is the tenant Id where I want to install the app

app["mdmId"] is the app Id that I want to install in given tenant

@Cindy de Araujo Soares Moore ,
@Renan Schroeder ,

Comment sent to JIRA TOTVS Brazil - https://jiraproducao.totvs.com.br/browse/DLABSCAPL-3624:

Iniciamos a trabalhar em sua issue e manteremos você informado!

Atenciosamente,
Equipe TOTVS LABS.

This card was initially PLANNED, however due to the high number of red-phones on the sprint this card is probably not going to have enough capacity to be finished on the dev cycle. That’s why, changing from PLANNED to NOT_PLANNED.

@Cindy de Araujo Soares Moore ,

@Geny Isam Hamud Herrera ,
Comment sent to JIRA TOTVS Brazil - https://jiraproducao.totvs.com.br/browse/DLABSCAPL-3624:

Informamos que esta issue foi incluída em uma sprint com previsão de entrega até 2023-12-11 (podendo ocorrer retorno antes). Não é necessário retornar esta interação, caso não tenha dúvidas. Qualquer alteração de planejamento será novamente notificada nesta issue.

Atenciosamente,
Equipe TOTVS LABS.

@Cindy de Araujo Soares Moore ,
@Geny Isam Hamud Herrera ,

This issue was planned to be delivered until 2023-12-11. You can check that by consulting the issue in the Due Date field.

Dates already planned for this issue: 2023-12-11

If External Issue Link field is filled, customer was also informed on JIRA TOTVS.

Message thread link on #red-phone channel:

https://totvslabs.slack.com/archives/C03NT4US9J9/p1697044577520779

@Cindy de Araujo Soares Moore ,
@MARCOS STUMPF , @Robson Thanael Poffo ,

This issue is pending for cloning and/or moving to Carol Backlog since you have just transitioned the issue status/column.

@Cindy de Araujo Soares Moore ,
@Robson Thanael Poffo ,

This issue is pending for Carol Backlog Review since you have just transitioned the issue status/column.

@Cindy de Araujo Soares Moore ,
@Robson Thanael Poffo ,

This issue is pending for UX Review since you have just transitioned the issue status/column.