Add shared inactive VuMark database to secrets files#3012
Merged
adamtheturtle merged 1 commit intomainfrom Feb 23, 2026
Merged
Conversation
Create a single inactive VuMark database (one per run, shared across all 100 secrets files) by mimicking the pattern used for inactive cloud databases: create a license, create the VuMark database, capture its credentials, then delete the license. This provides test fixtures with inactive VuMark database credentials alongside the existing inactive cloud database credentials. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
adamtheturtle
temporarily deployed
to
development
GitHub Actions
Inactive
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a single inactive VuMark database created once per run and shared across all 100 secrets files. This mirrors the pattern used for inactive cloud databases: create a license, create the VuMark database, capture its credentials, then delete the license to make it inactive. Each generated secrets file now includes credentials for an inactive VuMark database alongside the existing inactive cloud database credentials.
Co-Authored-By: Claude Sonnet 4.6 noreply@anthropic.com
Note
Low Risk
Changes are limited to an admin script and add extra resource creation/deletion plus new env vars; main risk is flakiness or failures during Selenium-driven setup rather than runtime behavior.
Overview
Secrets file generation now also provisions a single “inactive” VuMark database per run (create license + DB, capture credentials, then delete license) and reuses its credentials across all generated secrets files.
Each
vuforia_secrets_*.envfile gains newINACTIVE_VUMARK_*entries alongside the existing inactive cloud DB values, requiring an extra Chrome driver/login during setup.Written by Cursor Bugbot for commit a855d64. This will update automatically on new commits. Configure here.