Repository navigation
fix(e2e): enable user provisioning on the E2E test instances during deploy - #1380
Merged
dylan-openhands merged 1 commit intoOct 10, 2026
Merged
Conversation
…eploy The org E2E specs call POST /api/organizations/provision-user, which the app registers only when oem_user_creation_flow_enabled is on. The deploy script now sets that item when it writes the instance config back. Co-authored-by: openhands <openhands@all-hands.dev>
openhands-agent
requested review from
aivong-openhands,
dylan-openhands,
jlav and
mamoodi
as code owners
October 9, 2026 13:38
dylan-openhands
approved these changes
Oct 9, 2026
dylan-openhands
approved these changes
Oct 10, 2026
dylan-openhands
deleted the
fix/e2e-enable-user-provisioning-on-test-instances
branch
October 10, 2026 14:07
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
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.
Opened by an automated OpenHands agent.
Risk: 3/10 — the change touches only the deploy script for the internal test instances, and it changes one config value that is off by default.
Problem
Two E2E tests fail on every run because the test instances keep the user-provisioning feature turned off, and both tests need that feature to add a user to a new organization.
Description
The deploy script reads the instance config and writes it back during each upgrade. This PR makes the script set one config item,
oem_user_creation_flow_enabled, to1in that write-back. Every other value stays the same. A new unit test checks that the script turns on this item and keeps the other values.Evidence
006-org-management › create an org and provision the new user into itand011-automations › owner in a fresh org can create a prompt automation.POST /api/organizations/provision-user. The server answers405 Method Not Allowed. A 405 here means that the server does not have this route./api/organizations/provision-user.USER_PROVISIONING_ENABLEDis true. The Helm valueuserProvisioning.enabledsets that variable.oem_user_creation_flow_enabledsets that Helm value (replicated/openhands.yaml). The item defaults to0.scripts/replicated_deploy.shdeploys every release to the internal test instances. It writes the config back unchanged, so the item stays0.008-managed-key-ownership,013-super-admin-dashboard, and the second006test) use the same route. They are skipped or blocked today, so this change also unblocks them.Work items
@budgetstests and the@billingtests. Re-enable each test whose skip reason can be fixed.Verification
After the next release deploys to unstable, the next unstable E2E launch in ReportPortal should show both tests as passed.
Helm Chart Checklist
scripts/).