-
Notifications
You must be signed in to change notification settings - Fork 17
fix: Finally replace awkward one-liner to create system-wide enterprise role assignments #227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
pwnage101
merged 1 commit into
master
from
pwnage101/ENT-11568-fix-role-assignment-oneline
Aug 11, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This assignment seems net new, but you might ask how anybody's devstack ever worked without it.
Best I can tell, everybody eventually followed one wiki doc or another and several of them mention the
seed_enterprise_devstack_datamanagement command, so at some point everybody just runs that command. There was no way to get a complete working devstack for enterprise without running bothdev.provision.enterpriseANDseed_enterprise_devstack_data, and neither in isolation was sufficient.That's not necessarily a bad thing---we ask developers to run multiple commands in sequence all the time. But the problem was that both commands overlapped in purpose, including the creation of the enterprise_worker user. Worse, they both provisioned the same user differently, so the second one was the winner. This non-determinism is confusing, could lead to difficult to understand devstack bugs, and contributed to dead weight in our codebase.
My recent PR openedx/edx-enterprise#2662 helped draw a clear line between each script:
dev.provision.enterpriseis just the bare minimum to get the enterprise services to talk, andseed_enterprise_devstack_datawas for actually provisioning enterprise customers and enterprise users. No more overlap.As a result, that created a gap in this file, it was now missing a step to create the assignment for the enterprise service worker. One side-benefit of adding this missing step is that now launching a fresh devstack Codespace instance gets you a fully functioning devstack out of the box with fully communicating enterprise services.