Page MenuHomePhabricator

[lib][landing][web] Use getCommConfig to get API keys for Webpack builds
ClosedPublic

Authored by ashoat on Apr 7 2023, 10:58 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Dec 14, 11:56 PM
Unknown Object (File)
Sat, Dec 14, 11:56 PM
Unknown Object (File)
Sat, Dec 14, 11:56 PM
Unknown Object (File)
Sat, Dec 14, 11:55 PM
Unknown Object (File)
Sat, Dec 14, 11:39 PM
Unknown Object (File)
Thu, Dec 5, 8:23 PM
Unknown Object (File)
Thu, Dec 5, 8:23 PM
Unknown Object (File)
Thu, Dec 5, 8:16 AM
Subscribers

Details

Summary

Linear task: ENG-3229.

Now that we're using getCommConfig, these API keys can be specified with JSON files in keyserver/secrets instead of requiring patching package.json files with env var declarations.

Depends on D7354

Test Plan
  1. I created a valid keyserver/secrets/alchemy.json file
  2. I added a console.log to print the value of alchemyKey from getConfigs in lib/webpack/shared.cjs
  3. I made sure that it printed the right value when called from landing and web, in both dev and prod modes

I also made sure to set the corresponding env var on my production keyserver.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable