Prepare for new Orama API Keys

[avivkeller]

We need new NEW_ environment variables for new api keys

@nodejs/web-infra

[MattIPv4]

Which env vars need duplicating, NEXT_PUBLIC_ORAMA_ENDPOINT + NEXT_PUBLIC_ORAMA_API_KEY?

[avivkeller]

Which env vars need duplicating, NEXT_PUBLIC_ORAMA_ENDPOINT + NEXT_PUBLIC_ORAMA_API_KEY?

cc @micheleriva

[micheleriva]

FYI, breaking news, we're having the new Orama Cloud in general availability on August 4th. I'd recommend making any change then (we'll obviously provide all the information and support)

[avivkeller]

We will be using _NEW prefixes, once the variables are ready

[MattIPv4]

Noting it here for posterity, I have added new Actions secrets NEW_ORAMA_PRODUCTION_DATASOURCE_ID + NEW_ORAMA_PRODUCTION_PRIVATE_API_KEY in this repo as provided by @micheleriva.

[MattIPv4]

Will need assistance from @ovflowd or @bmuenzenmeyer to set NEXT_PUBLIC_NEW_ORAMA_PROJECT_ID=939d8d74-dbb7-4098-ac46-00325a783e17 + NEXT_PUBLIC_NEW_ORAMA_API_KEY=c1_dRV3iUW4GpJkKffpYXgCEamhWLf$_X9gfYdiVhZkVD4MCr105K0qb$BiGdg for production in Vercel, as I appear to only have access to pre-prod env vars there.

[avivkeller]

(Note that the values above are not sensitive, and can be plaintext in comments like this)

[bmuenzenmeyer]

I'm out of the country right now on vacation. Be back next week

[MattIPv4]

Also noting it here for posterity, I have added new Actions secrets NEW_ORAMA_DATASOURCE_ID + NEW_ORAMA_PRIVATE_API_KEY in this repo as provided by @micheleriva. I've also set NEXT_PUBLIC_NEW_ORAMA_PROJECT_ID + NEXT_PUBLIC_NEW_ORAMA_API_KEY in Vercel for the Preview environment.

[MattIPv4]

I've also set NEXT_PUBLIC_NEW_ORAMA_DATASOURCE_ID for Preview in Vercel per #7971 (comment)

[MattIPv4]

With @ovflowd's assistance, signed into the Vercel infra account and have now set NEXT_PUBLIC_NEW_ORAMA_PROJECT_ID + NEXT_PUBLIC_NEW_ORAMA_API_KEY + NEXT_PUBLIC_NEW_ORAMA_DATASOURCE_ID in production, so we should be good to go now!