Skip to content

Bump vws-web-tools and add VuMark tooling#2930

Merged
adamtheturtle merged 3 commits intomainfrom
adamtheturtle/vumark-secrets
Feb 16, 2026
Merged

Bump vws-web-tools and add VuMark tooling#2930
adamtheturtle merged 3 commits intomainfrom
adamtheturtle/vumark-secrets

Conversation

@adamtheturtle
Copy link
Member

@adamtheturtle adamtheturtle commented Feb 16, 2026

Summary

  • Bumped vws-web-tools from 2026.2.16 to 2026.2.16.1 to access new VuMark database functions
  • Extended admin/create_secrets_files.py to create VuMark databases alongside regular cloud databases
  • VuMark databases only have server-side access keys (no client keys)
  • Updated vuforia_secrets.env.example template with new VuMark credentials fields

Test plan

  • Run the admin/create_secrets_files.py script to generate test secrets with VuMark credentials
  • Verify generated files contain both regular database and VuMark database credentials

Note

Medium Risk
Moderate risk because it changes automation that provisions real Vuforia resources and writes new secret material; failures/timeouts could increase resource churn or break local test setup.

Overview
Updates the admin/create_secrets_files.py secrets generator to also create a VuMark database per run and write its server credentials into each generated .env file, refactoring the provisioning flow into helper functions with explicit timeout handling.

Bumps vws-web-tools to 2026.2.16.1 to use the new VuMark creation/detail APIs, and extends vuforia_secrets.env.example with the new VUMARK_* environment variables (server keys only).

Written by Cursor Bugbot for commit b1e0e8d. This will update automatically on new commits. Configure here.

…ools

Bump vws-web-tools to 2026.2.16 and update driver setup
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

VUMARK_VUFORIA_SERVER_SECRET_KEY={vumark_details["server_secret_key"]}

INACTIVE_VUMARK_VUFORIA_TARGET_MANAGER_DATABASE_NAME={os.environ["INACTIVE_VUMARK_VUFORIA_TARGET_MANAGER_DATABASE_NAME"]}
INACTIVE_VUMARK_VUFORIA_SERVER_SECRET_KEY={os.environ["INACTIVE_VUMARK_VUFORIA_SERVER_SECRET_KEY"]}
Copy link

Choose a reason for hiding this comment

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

Missing inactive VuMark server access key in secrets

High Severity

The inactive VuMark credentials section is missing INACTIVE_VUMARK_VUFORIA_SERVER_ACCESS_KEY. The active VuMark section correctly includes VUMARK_VUFORIA_SERVER_ACCESS_KEY alongside the secret key, but the inactive VuMark section only has the database name and INACTIVE_VUMARK_VUFORIA_SERVER_SECRET_KEY, omitting the corresponding access key. This is inconsistent with the active VuMark pattern and with how regular (non-VuMark) inactive credentials mirror their active counterparts. The same omission is present in vuforia_secrets.env.example.

Additional Locations (1)

Fix in Cursor Fix in Web

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@adamtheturtle adamtheturtle merged commit baa4028 into main Feb 16, 2026
11 checks passed
@adamtheturtle adamtheturtle deleted the adamtheturtle/vumark-secrets branch February 16, 2026 15:06
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.

1 participant