Skip to content

set-test-tokens: use env vars as default for secret/key/url - #256

Open
stephen-derosa wants to merge 1 commit into
mainfrom
sderosa/set-test-tokens-env-vars-are-default
Open

set-test-tokens: use env vars as default for secret/key/url#256
stephen-derosa wants to merge 1 commit into
mainfrom
sderosa/set-test-tokens-env-vars-are-default

Conversation

@stephen-derosa

Copy link
Copy Markdown
Collaborator

No description provided.

@stephen-derosa stephen-derosa self-assigned this Sep 8, 2026
Copilot AI lite review requested due to automatic review settings September 8, 2026 14:34
devin-ai-integration[bot]

This comment was marked as resolved.

This comment was marked as resolved.

@stephen-derosa
stephen-derosa force-pushed the sderosa/set-test-tokens-env-vars-are-default branch from 46afef4 to 2023910 Compare September 8, 2026 20:58
LIVEKIT_URL="ws://localhost:7880"
_grant_json='{"canPublish":true,"canSubscribe":true,"canPublishData":true}'

echo "set_test_tokens: Using LIVEKIT_URL: $LIVEKIT_URL" >&2

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: Can we avoid printing here? We have plenty of logs across SDK layers/end products (ROS Portal) that log which URL is being connected to. I also run individual tests often and call into this script first, so I'll be getting more output

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we need some log to indicate the creds being used so we can prevent devs from using the wrong creds. I could change it to "using local server" or "using cloud server" ?

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.

3 participants