Skip to content

Configure opentest credentials for Bubble real-API CI #3

Closed

Description

@kvz

Why

The modernization PR #2 runs the built Bubble element against the real Transloadit API, but this repository has no configured secrets. Both Node check jobs pass; the internal-PR e2e job fails explicitly before uploading because its credentials are missing (run).

Maintainer action

Add these names to repository Actions secrets and Dependabot secrets, using the existing opentest credentials (never paste their values in this issue):

  • BUBBLE_E2E_TRANSLOADIT_KEY
  • BUBBLE_E2E_TRANSLOADIT_SECRET

Then rerun the failed e2e job on #2. No Template ID is needed: the test signs temporary image resize Instructions and creates no Template. The same test passes locally with node-sdk's existing .env loaded directly into the process environment.

Refs #1. This tracks only CI configuration; actual Bubble test-app verification and marketplace publication are separate login-dependent acceptance steps documented in #2.

🤖 Claimed by kvz on framework1/bubble-plugin since 2026-10-30 · resume: codex resume 01a18956-04ed-7730-8e93-34911ec3771e

Activity

  1. self-assigned this
    on Oct 29, 2026
  2. kvz commented on Oct 29, 2026

    @kvz
    MemberAuthor

    Both BUBBLE_E2E_TRANSLOADIT_KEY and BUBBLE_E2E_TRANSLOADIT_SECRET are now configured as repository Actions secrets and Dependabot secrets; their names were verified without reading or printing values.

    Run 40971116032, attempt 2 completed successfully on fda7414164fd467266d3c2733defa1e00d433106. The real-API e2e job passed 12 tests with no skips, including signed file upload, processing and result verification. Both Node check jobs also pass.

    Closing this CI configuration issue. Bubble test-app installation, editor acceptance and publication remain with Kevin under #1; those handoff steps are unchanged.

    Revive Bubble uploads with current Uppy and tested release candidates — open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions