feat(galaxy|access): "appdata" 128kb storage api

[Cosmin-Parvulescu]

Description

• Added storage menu item
• Added early access panel for pro plan (this still needs copy and alignment on what info we display)
• Added hidden storage page with functionality (this still needs copy and alignment on what info we display)
• Updated toggle input props to handle lack of label
• Added gql schemas for get / set external app data
• Added authorization resolver to handle external app data
• Added external app data packages, notably STARTER
• Added new KV for usage categories (will hold reads / writes for the get / set endpoints for app data, and others in the future)
• Added external app data endpoints in worker & durable objects
• Added new middleware for validating existance of both JWT and X-GALAXY-KEY in requests to Galaxy

Related Issues

• Closes feat(galaxy|access): "appdata" 128kb storage api #1950

Testing

Console

1. Create an app
2. Go to storage
3. Go to <current_url>/ostrich
4. Toggle on the feature

Galaxy

1. Using Yoga (http://localhost:10401/), select the get / set query / mutation
2. In the Headers section add the following:

{
  "Authorization": "Bearer <an app user's jwt>",
  "X-GALAXY-KEY": "API key from Auth tab in Console"
}

3. Run queries / mutations, be aware that the payload has to be an escaped JSON like { /"foo/":/"bar/"}
4. Marvel

Profile

1. Authenticate to Profile app
2. Throw this code in the profile.tsx route

export const loader: LoaderFunction = async ({ request, context }) => {
  const jwt = await requireJWT(request, context.env)
  const galaxyClient = await getGalaxyClient(
    {
      ...generateTraceContextHeaders(context.traceSpan),
      ...getAuthzHeaderConditionallyFromToken(jwt),
      ...{
        'X-GALAXY-KEY': ‘<galaxy_api_key>’,
      },
    },
    context.env
  )

  await galaxyClient.setExternalData({
    payload: {
      foo: 'bar',
      biz: 'baz',
    },
  })

  const { externalData } = await galaxyClient.getExternalData()

  console.log(JSON.stringify(externalData, null, 2))

  return null
}

Checklist

• I have read the CONTRIBUTING guidelines
• I have tested my code (manually and/or automated if applicable)
• I have updated the documentation (if necessary)

[betimshahini]

Let's name this STARTER, to future-proof it a little.

[betimshahini]

Externalize this into function that gives you the usage key.

[betimshahini]

Let's rename references of this to *ExternalAppData, here and everywhere else in the PR, to differentiate it from future external data features.

[betimshahini]

Same as previous comment on externalizing this into a function.

[betimshahini]

This and the await below should be run concurrently

[betimshahini]

This and promise below should run concurrently.

[betimshahini]

I think the env-specific wrangler files would also need to be updated.

[Cosmin-Parvulescu]

Yes, I'll update them once we reach the final design.

[betimshahini]

This key name and the one below for the next function don't match.

[betimshahini]

Shouldn't this be set statically in code (map or object) as opposed to being calculated at runtime?

[betimshahini]

@Cosmin-Parvulescu copy for early access panel and service description inside storage page:
App Data Storage service provides a hassle-free way to store and retrieve per-user data for your application. Once activated, the service can be accessed through our Galaxy API and it supports storing data up to 128kb, per user.

Remove API URL from currently-hidden app data storage page itself.

[betimshahini]

In the case of external storage not being defined, the error exposed through Galaxy is 400 Bad request, yet the TRPC one comes through correctly as external storage not enabled

[betimshahini]

Related to comment above, when external storage is not enabled, this returns false as opposed to throwing the exception being thrown for the getExternalAppData query.

[betimshahini]

This is good to go; will be approved and merged once #2743 is in.