Skip to content
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

Use 'flowcrypt.com/shared-tenant-fes' instead of 'flowcrypt.com/api' #2171

Merged
merged 62 commits into from
Mar 13, 2023

Conversation

DenBond7
Copy link
Collaborator

@DenBond7 DenBond7 commented Jan 23, 2023

This PR added using 'flowcrypt.com/shared-tenant-fes' instead of 'flowcrypt.com/api'

close #2162
close #2138


Tests (delete all except exactly one):

  • Tests added or updated

todo


To be filled by reviewers

I have reviewed that this PR... (tick whichever items you personally focused on during this review):

  • addresses the issue it closes (if any)
  • code is readable and understandable
  • is accompanied with tests, or tests are not needed
  • is free of vulnerabilities

@DenBond7 DenBond7 requested a review from tomholub January 23, 2023 14:40
@DenBond7 DenBond7 requested a review from tomholub January 25, 2023 09:33
@DenBond7
Copy link
Collaborator Author

@tomholub Please relook the current changes while I'm working on fixing tests.

@DenBond7 DenBond7 requested a review from tomholub January 25, 2023 13:14
@DenBond7
Copy link
Collaborator Author

@tomholub Please relook. I've added the requested changes.

Copy link
Collaborator

@tomholub tomholub left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's improving a lot, see comments

@DenBond7
Copy link
Collaborator Author

DenBond7 commented Mar 9, 2023

@tomholub I think I've added changes that were requested to migrate to shared-tenant-fes. But all of these changes are related to the setup screen. we still don't support the following:

going forward, client continues attempting to call fes.domain.com first before falling back on flowcrypt.com/shared-tenant-fes anytime it needs to update Client Configuration, and continues using flowcrypt.com/shared-tenant-fes for password protected messages and all other APIs, for as long as fes.domain.com is not available.
if Client Configuration is ever successfully retrieved from fes.domain.com, the app will start using fes.domain.com for all APIs going forward.

it means we decide at the setup screen whether will we use a custom FES server or not. After the setup screen, we don't use a custom FES server if it failed at the setup screen.

If it is possible I propose adding that functionality via a separate PR. The current PR is already not simple.

If yes, I will ask Mart to recheck #2197 and after that, we will be ready to merge it.

@tomholub
Copy link
Collaborator

tomholub commented Mar 9, 2023

yes, the parts after setup can be done in a future version. so ok for @martgil to re check functionality now

@DenBond7 DenBond7 marked this pull request as ready for review March 13, 2023 09:23
@DenBond7 DenBond7 requested a review from ioanmo226 March 13, 2023 09:24
@DenBond7
Copy link
Collaborator Author

@ioanmo226 Please make the final review.

@ioanmo226
Copy link
Collaborator

ioanmo226 commented Mar 13, 2023

Can I merge this PR with after my review? or waiting some other things?

@DenBond7
Copy link
Collaborator Author

Can I merge this PR with after my review? or waiting some other things?

Yes, we are ready to merge it.

Copy link
Collaborator

@ioanmo226 ioanmo226 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@ioanmo226 ioanmo226 merged commit ad44f9d into master Mar 13, 2023
@ioanmo226 ioanmo226 deleted the issue_2162_shared-tenant-fes branch March 13, 2023 12:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants