Update LaunchDarkly Flags SDK template for Marketplace integration#1525
Conversation
|
@Andrewjeska is attempting to deploy a commit to the Vercel Labs Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
289a8ec to
6289a25
Compare
There was a problem hiding this comment.
I think this is just the linter
|
Deployment failed with the following error: Learn More: https://vercel.com/docs/concepts/projects/project-configuration |
| * This adapter supports two ways of reading LaunchDarkly flags, and picks one | ||
| * automatically based on which environment variables are present: | ||
| * | ||
| * 1. Edge Config mode (`EDGE_CONFIG` or `EXPERIMENTATION_CONFIG`, plus |
There was a problem hiding this comment.
This template originally had EDGE_CONFIG, probably the connected account integration expected that env var. let me know what's the preferred env var now.
| 2. Generate a `FLAGS_SECRET` yourself instead of relying on the deploy prompt: | ||
|
|
||
| ```bash | ||
| node -e "console.log(crypto.randomBytes(32).toString('base64url'))" | ||
| ``` |
There was a problem hiding this comment.
I'm not too familiar, can you just do this?
Summary
Updates the
flags-sdk/launchdarklyexample to work cleanly with the LaunchDarkly integration on the Vercel Marketplace.EXPERIMENTATION_CONFIG)LAUNCHDARKLY_SDK_KEY), no Edge Config required. Addslib/launchdarkly-adapter.ts..env.examplerewritten to explain which vars the integration injects vs. which you set, both modes, and a manual-setup path (including generatingFLAGS_SECRET).Testing
pnpm build/ local dev in both Edge Config and server SDK modes.