Skip to content
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions cms/djangoapps/contentstore/toggles.py
Original file line number Diff line number Diff line change
Expand Up @@ -542,3 +542,15 @@ def enable_course_optimizer_check_prev_run_links(course_key):
Returns a boolean if previous run course optimizer feature is enabled for the given course.
"""
return ENABLE_COURSE_OPTIMIZER_CHECK_PREV_RUN_LINKS.is_enabled(course_key)


# .. toggle_name: authz.enable_course_authoring
# .. toggle_implementation: CourseWaffleFlag
# .. toggle_default: False
# .. toggle_description: This toggle will enable the new openedx-authz authorization engine for course authoring.
# .. toggle_warning: Enabling this toggle will trigger a data migration to move role assignations between the legacy and the openedx-authz system.
# .. toggle_use_cases: temporary
# .. toggle_creation_date: 2026-02-05
# .. toggle_target_removal_date: 2027-06-09
# .. toggle_tickets: https://github.com/openedx/openedx-platform/issues/37927
AUTHZ_COURSE_AUTHORING_FLAG = CourseWaffleFlag('authz.enable_course_authoring', __name__)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Would this flag need to be available to the LMS (i.e. Instructor Dashboard)?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Good question, the only flow that I know for sure would technically be on the LMS is the course team management that is also available on the Instructor Dashboard.

Do you think this flag should live elsewhere because of that? I'm not sure where it would be a good place to put it, any suggestions?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Yeah, if we do anticipate using it in the course team management, I think we would want it in a common location such as openedx/core/toggles.py. @bmtcril Any input on where it makes sense to define the flag?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Given that it's fairly tightly bound to CourseOverview I think it would be fair to put it in openedx/core/djangoapps/course_overviews where both sides can get at it. openedx/core/toggles.py would also make sense to me. I'll ask around at our standup for opinions, though.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Seems like openedx/core/toggles.py is the consensus!

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Thanks! I'll do the change

Loading