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 mu-haskell to implement one initial federation request across backends #1319

Merged
merged 172 commits into from
Feb 22, 2021

Conversation

jschaul
Copy link
Member

@jschaul jschaul commented Jan 6, 2021

Copy link
Contributor

@fisx fisx left a comment

Choose a reason for hiding this comment

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

I'll keep reviewing later, probably tonight.

docs/reference/config-options.md Outdated Show resolved Hide resolved
libs/dns-util/src/Wire/Network/DNS/Helper.hs Outdated Show resolved Hide resolved
libs/dns-util/src/Wire/Network/DNS/Helper.hs Outdated Show resolved Hide resolved
akshaymankar and others added 2 commits February 16, 2021 15:38
This makes the use more futureproof as it guards against any cleanup the
`withResolver` function might want to do after a resolver is used.

This means the whole federator needs to run inside `withResolver`, but I cannot
really see any downsides to this.
Co-authored-by: fisx <mf@zerobuzz.net>
Copy link
Contributor

@fisx fisx left a comment

Choose a reason for hiding this comment

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

General question: can we move https://github.com/wearezeta/documentation/blob/master/topics/federation/federation-design.md to wire-server/docs now? Or to wire-docs? The documentation repo is deprecated by confluence anyway.

More review chunks coming up!

libs/wire-api-federation/proto/router.proto Show resolved Hide resolved
libs/wire-api-federation/proto/router.proto Show resolved Hide resolved
libs/wire-api-federation/proto/router.proto Outdated Show resolved Hide resolved
libs/wire-api-federation/proto/router.proto Outdated Show resolved Hide resolved
LocalCall -> Request
RemoteCall -> FederatedRequest
RouteToRemote -> Outward
RouteToLocal and RouteToInternal -> Inward

Function names have also been adjusted in many places.

We still have modules externalServer internalServer and 'Remote' in
federator. Perhaps we should also rename the 'remote' module?
Copy link
Member

@akshaymankar akshaymankar left a comment

Choose a reason for hiding this comment

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

As decided in the call, let's merge this.
@fisx (or others) feel free to continue to review this, let's try to incorporate the changes in further PRs.

@jschaul jschaul merged commit f683299 into develop Feb 22, 2021
@jschaul jschaul deleted the mu branch February 22, 2021 12:58
akshaymankar added a commit that referenced this pull request Feb 24, 2021
This reverts commit 04fda73.
This commit was squashed in #1319.
@arianvp arianvp mentioned this pull request Feb 26, 2021
arianvp added a commit that referenced this pull request Feb 26, 2021
## Bug fixes and other updates

* Pin kubectl image in sftd chart (#1383)
* Remove imagePullPolicy: Always for reaper chart (#1387)


## Internal changes

* Use mu-haskell to implement one initial federation request across backends (#1319)
* Add migrate-external-ids tool (#1384)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants