init.sh

#!/usr/bin/env bash

set -o errexit
set -o pipefail
set -o nounset

# TODO(johnny): We should update `flowctl` to accept a refresh token via `flowctl auth token --token $REFRESH_TOKEN`
# It should take ownership of the provided refresh token rather than create a new one, as it does today.
# It also must handle secret rotation for non-multi-use refresh tokens, as this one is.

# ui/src/services/gitpod.ts
# This object is generated in the dashboard and has to stay in sync
ACCESS_TOKEN_PARAMS=$(echo "$F_S" | base64 -d | jq -c -r '{"refresh_token_id": .rt.id, "secret": .rt.secret}')
DRAFT_ID=$(echo "$F_S" | base64 -d | jq -c -r '.id')

# The --data below maps {id, secret} into {refresh_token_id, secret},
# which are the parameters expected by `generate_access_token`.
# As this is a single-use token, we can only do this one time.
ACCESS_TOKEN=$(
    curl \
        -XPOST \
        -H "apikey: $FLOW_SUPABASE_ANON_TOKEN" \
        -H "Content-Type: application/json" \
        "https://$FLOW_SUPABASE_HOST/rest/v1/rpc/generate_access_token" \
        --data "$ACCESS_TOKEN_PARAMS" \
        --silent \
    | jq -r -c '.access_token'
)

# Ask flowctl to create a persistent refresh token, which will be available
# in subsequent starts of the development container.
flowctl auth token --token "$ACCESS_TOKEN"

# Select and fetch the user's draft.
flowctl draft select --id "$DRAFT_ID" > /dev/null
flowctl draft develop --target /workspace/flow/flow.yaml

echo "Welcome to the Flow development container. View README for help getting started."