Skip to content

Cedric/flag for ci#30

Merged
Cedric / ViaDézo1er (viadezo1er) merged 1 commit into
mainfrom
cedric/flag-for-ci
May 20, 2026
Merged

Cedric/flag for ci#30
Cedric / ViaDézo1er (viadezo1er) merged 1 commit into
mainfrom
cedric/flag-for-ci

Conversation

@viadezo1er
Copy link
Copy Markdown
Collaborator

@viadezo1er Cedric / ViaDézo1er (viadezo1er) commented May 11, 2026

The goal is to allow us to eval spark against test apps.
As a user, be warned: we are not expecting you to use these flags. We may remove or change them without any warning.

Add BRAINTRUST_SPARK_INSTRUMENT, BRAINTRUST_SPARK_YOLO, BRAINTRUST_SPARK_API_KEY, BRAINTRUST_SPARK_PROJECT_ID, BRAINTRUST_SPARK_PROVIDER, and BRAINTRUST_SPARK_PROVIDER_API_KEY env vars to allow spark to be used by scripts (useful for CI).
BRAINTRUST_SPARK_YOLO also tweaks the prompt to warn the agent that there isn't any user to answer the questions.
Is it ok? It means we would be evaluating something that isn't what the users will actually experience.

BRAINTRUST_SPARK_YOLO implies BRAINTRUST_SPARK_INSTRUMENT. Keeping the 2 flags separate allows to test how much can be done before asking questions to the user.

Azure, Vertex, Bedrock, custom llm providers are not handled.

Removes CRANK_ENABLE_TELEMETRY mention from the help that was added in preparation for telemetry, before telemetry was postponed.

@viadezo1er Cedric / ViaDézo1er (viadezo1er) changed the base branch from main to cedric/revamp-onboarding-telemetry May 11, 2026 23:15
…UST_SPARK_API_KEY, BRAINTRUST_SPARK_PROJECT_ID, BRAINTRUST_SPARK_PROVIDER, and BRAINTRUST_SPARK_PROVIDER_API_KEY env vars for CI/script use
@viadezo1er Cedric / ViaDézo1er (viadezo1er) merged commit 524969e into main May 20, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants