Page MenuHomePhabricator

[keyserver][lib][web] Make it possible to call getCommConfig from Webpack config
ClosedPublic

Authored by ashoat on Apr 7 2023, 10:40 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Nov 8, 9:23 PM
Unknown Object (File)
Fri, Nov 8, 9:23 PM
Unknown Object (File)
Fri, Nov 8, 9:23 PM
Unknown Object (File)
Fri, Nov 8, 9:21 PM
Unknown Object (File)
Fri, Nov 8, 3:19 AM
Unknown Object (File)
Wed, Nov 6, 3:29 AM
Unknown Object (File)
Tue, Nov 5, 2:10 AM
Unknown Object (File)
Tue, Nov 5, 2:06 AM
Subscribers

Details

Summary

Linear task: ENG-3229.

We have three configs that we need to be accessible from the Webpack build:

  1. COMM_ALCHEMY_KEY
  2. COMM_WALLETCONNECT_KEY
  3. Coming soon: config for identity service

Currently it's a huge pain to configure these in a dev environment. keyserver configs can be imported via getCommConfig, but it doesn't work in other environments.

This diff makes it possible to call getCommConfig from web.

Depends on D7351

Test Plan

I tested with this patch: https://gist.github.com/Ashoat/487aa5a611e84f1751d7c60d82b8e4f9

I made sure that it printed the contents of commapp_url.json when called from landing and web, in both dev and prod modes.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Harbormaster returned this revision to the author for changes because remote builds failed.Apr 7 2023, 10:54 AM
Harbormaster failed remote builds in B18118: Diff 24819!

Most of this diff is plumbing to make it possible for web and landing to access the Babel-transpiled (Flow-stripped) dist file that keyserver is set up to generate

ashoat requested review of this revision.Apr 7 2023, 3:17 PM
This revision is now accepted and ready to land.Apr 7 2023, 3:27 PM