forked from centrifugal/centrifugo
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat/migracao cloud centrifugo #8
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jeancabral
force-pushed
the
feat/migracao-cloud-centrifugo
branch
from
December 7, 2021 19:25
ff41af5
to
0a0bf49
Compare
jeancabral
force-pushed
the
feat/migracao-cloud-centrifugo
branch
from
December 8, 2021 20:24
4685113
to
85a54bb
Compare
jeancabral
force-pushed
the
feat/migracao-cloud-centrifugo
branch
from
December 10, 2021 11:12
2b6f90c
to
b35ca89
Compare
jeancabral
force-pushed
the
feat/migracao-cloud-centrifugo
branch
from
December 14, 2021 18:13
a9c5280
to
6322944
Compare
jeancabral
force-pushed
the
feat/migracao-cloud-centrifugo
branch
from
December 15, 2021 15:50
5372e17
to
8c8ec74
Compare
jeancabral
force-pushed
the
feat/migracao-cloud-centrifugo
branch
from
December 15, 2021 15:57
8c8ec74
to
3a79f2e
Compare
jeancabral
requested review from
andremacdowell,
GabrielSouzaHub,
gmarcial,
jonathanlazaro1,
leoferlopes and
ViniciusLinharesAO
December 16, 2021 13:07
gmarcial
approved these changes
Dec 16, 2021
andremacdowell
approved these changes
Dec 16, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivo da mudança
Na sexta feira dia 03/12/21 o SOC reportou um problema de segurança na aplicação do Centrífugo e desativou o DNS externo. Com a remoção do DNS as aplicações do front do Celebro pararam de receber os feedbacks de criação de caso automático no Salesforce em tempo real.
Para resolver o problema tivemos que migrar o Centrífugo para o cloud do GKE para tratar a falha de segurança identificada.
Qual o tipo dessa mudança?
Em qual ambiente será aplicada a mudança?
Qual o risco aplicado a essa mudança?
Existe um plano de rollback automatizado?
Em caso de Rollback Manual, explique o processo.
Disparar a última release produtiva a partir do VSTS.
Links das demandas que estão sendo resolvidas com a mudança.
Teste de funcionalidade foi realizado? (Antes de colocar em produção)
Há evidências de teste?
Descreva como foi o teste e coloque em anexo as evidências.
Foi feito as alterações do dns e da secret em ambiente de Staging do novo centrifugo na aplicações Go-Agent e Iris. Ao abrir o Agent Dashboard foi verificado a conexão com o centrifugo e feito uma alteração de cadastro de endereço, com isso, e foi observado o comportamento em que a Iris retorna o feedback dos "steps" do processo no front do celebro em tempo real.
Quem são os aprovadores?