Bring your own project
navigator ops gcp setup provisions into a project; it does not create one. Start by creating a project and attaching
a billing account, then authenticate so the CLI can act as you:
gcloud projects create your-project-id --name "Neon Law Navigator"
gcloud billing projects link your-project-id --billing-account "$BILLING_ACCOUNT_ID"
gcloud auth login --force --update-adc
gcloud auth print-access-token >/dev/null
gcloud auth application-default print-access-token >/dev/null
Before provisioning, confirm billing is enabled for every selected project. Load each row from the operator-managed root; check a separate registry project too when your installation uses one:
for CONFIG in "$NAVIGATOR_DEPLOYMENTS_DIR"/deployments/*/config.toml; do
set -a; eval "$(grep ' = "' "$CONFIG" | sed 's/ = /=/')"; set +a
gcloud billing projects describe "$NAVIGATOR_GCP_PROJECT_ID" \
--format='value(projectId,billingEnabled)'
done
Each selected runtime project must show True. If a row is False, attach billing before running setup. Check a
registry project by supplying its operator-managed ID:
gcloud billing projects describe "$NAVIGATOR_IMAGE_REGISTRY_PROJECT" \
--format='value(projectId,billingEnabled)'