utels-project-bootstrap

Register utels projects and set up ingest tokens by running the setup script with environment variables for production and staging targets. The script provisions tokens via REST calls and injects them directly into wrangler secrets without exposing them in shell output.

Yes, you can bootstrap a utels project for only staging by passing the --only flag to limit targets. This restricts the token provisioning and wrangler secrets injection to the specified environment.

Provisioning utels ingest tokens requires UTELS_BOOTSTRAP_TOKEN, APP_UTELS_PROJECT_PROD, APP_UTELS_PROJECT_STAGING, and UTELS_ENDPOINT environment variables. An optional DRY_RUN variable is also supported for testing without side effects.

Store ingest tokens securely by using the bootstrap script, which automatically captures the token from the REST response and writes it to wrangler secrets. This prevents secret leakage by avoiding shell stdout during the injection process.

Yes, you can test utels project registration without side effects by enabling the DRY_RUN environment variable. This simulates the token provisioning and secrets injection workflow without applying changes to wrangler.

Yes, utels project bootstrap supports custom deployment endpoints by configuring the UTELS_ENDPOINT environment variable. This allows targeting different utels deployments for project registration and token provisioning.