Skip to content

feat: implement authz schema loading pipeline - #446

Draft
rodmgwgu wants to merge 1 commit into
rod/authz-schema-filesfrom
rod/authz-schema-loader
Draft

feat: implement authz schema loading pipeline#446
rodmgwgu wants to merge 1 commit into
rod/authz-schema-filesfrom
rod/authz-schema-loader

Conversation

@rodmgwgu

Copy link
Copy Markdown
Contributor

Problem

Authorization schema definitions need to be discovered, compiled, validated, rendered, and loaded into the database, with a management command and persistence models to support it.

Approach

Implements the full pipeline and supporting code:

  • openedx_authz/engine/schema/ — discovery, compilation, validation, loading, pipeline, types, exceptions
  • openedx_authz/engine/renderer.py — schema rendering
  • openedx_authz/management/commands/load_authz_schema.py — management command
  • openedx_authz/models/schema.py + migration 0011_authz_schema_definitions.py
  • MANIFEST.in / setup.py packaging updates for the YAML data files
  • tests under openedx_authz/tests/schema/

Rollback plan

Revert this PR to remove the pipeline; the schema YAML files (PR 2) and ADR (PR 1) remain but are inert without this code. The new migration is additive; roll back by reverting and running the reverse migration if applied.


Stack (3/3):

  1. docs: add ADR for authorization schema source tracking #444 — ADR doc
  2. feat: add authz schema definition files #445 — authz schema YAML files
  3. This PR — schema loading pipeline (base: rod/authz-schema-files)

Base is the PR 2 branch; review only the incremental diff. Merge last, after #444 and #445.

Merge checklist:

Adds the schema discovery, compilation, validation, rendering and
loading pipeline, the load_authz_schema management command, schema
models and migration, and supporting tests. Part 3 of the stack.
@openedx-webhooks openedx-webhooks added open-source-contribution PR author is not from Axim or 2U core contributor PR author is a Core Contributor (who may or may not have write access to this repo). labels Sep 10, 2026
@openedx-webhooks

openedx-webhooks commented Sep 10, 2026

Copy link
Copy Markdown

Thanks for the pull request, @rodmgwgu!

This repository is currently maintained by @openedx/committers-openedx-authz.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.
🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads
🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

🔘 Update the status of your PR

Your PR is currently marked as a draft. After completing the steps above, update its status by clicking "Ready for Review", or removing "WIP" from the title, as appropriate.


Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

@github-project-automation github-project-automation Bot moved this to Needs Triage in Contributions Sep 10, 2026
@rodmgwgu
rodmgwgu marked this pull request as draft September 10, 2026 18:36
@rodmgwgu
rodmgwgu added this pull request to stack #447 September 10, 2026 18:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core contributor PR author is a Core Contributor (who may or may not have write access to this repo). open-source-contribution PR author is not from Axim or 2U

Projects

Status: Needs Triage

Development

Successfully merging this pull request may close these issues.

2 participants