Commit 9cd5046
Tailwind UI rebuild, legacy authorization, OS surface removals
Hand the authorization layer off to dojo-pro. OS keeps a legacy
``is_superuser`` / ``is_staff`` / ``authorized_users`` model and the
seven RBAC + Dojo_Group classes survive as ``managed=False`` shells in
``dojo/authorization/models.py`` so historical pro migrations
(``pro.0001_plugiun_consolidation`` ``EnhancedDojoGroup.group``,
``pro.0034_pghistory_for_permissions_models`` proxy bases) keep
resolving when Django reloads project state. OS code makes no
runtime references to Pro.
Single ``dojo.0268_release_authorization_to_pro`` migration folds:
- Re-introduces ``authorized_users`` M2M on Product / Product_Type and
backfills it from the RBAC tables (Member / Group → flat membership;
Global_Role(Owner|Writer|Maintainer|API_Importer) → ``is_superuser`` /
``is_staff``).
- Drops the redundant post-RBAC ``members`` / ``authorization_groups``
M2M accessors on Product / Product_Type (the through-tables remain).
- Flips the eight authorization shells to ``managed=False`` and pins
their ``db_table``s.
- ``RemoveField``s ``default_group`` / ``default_group_role`` /
``default_group_email_pattern`` from ``dojo_system_settings`` (Pro
copies the values onto ``EnhancedSystemSettings`` first via
``run_before``).
Plus the Tailwind UI rebuild and the OS surface tidying that this
branch was already carrying.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>1 parent 558a3d2 commit 9cd5046
678 files changed
Lines changed: 48740 additions & 17298 deletions
File tree
- components
- node_modules
- docs/content
- admin
- sso
- user_management
- automation/api
- releases
- os_upgrading
- pro
- dojo
- announcement
- api_v2
- asset
- api
- auditlog
- ui
- authorization
- banner
- benchmark
- components
- db_migrations
- development_environment
- endpoint
- engagement
- finding_group
- finding
- fixtures
- github
- templates/dojo
- ui
- group
- home
- importers
- jira
- api
- location
- api
- management/commands
- metrics
- note_type
- notes
- notifications
- templates/notifications
- ui
- object
- organization
- api
- product_type
- product
- regulations
- reports
- risk_acceptance
- search
- settings
- sla_config
- sso
- attribute_maps
- templates/dojo
- static/dojo
- css
- classic
- files
- js
- classic
- vendor
- survey
- system_settings
- templates_classic
- defectDojo-engagement-survey
- dojo
- breadcrumbs
- snippets
- url
- issue-trackers
- jira_full
- jira_limited
- login
- notifications
- alert
- mail
- msteams
- slack
- webhooks
- subtemplates
- templates
- defectDojo-engagement-survey
- dojo
- partials
- snippets
- url
- login
- templatetags
- test_type
- test
- tool_config
- tool_product
- tool_type
- url
- api
- ui
- user
- tests
- unittests
- authorization
Some content is hidden
Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
61 | 61 | | |
62 | 62 | | |
63 | 63 | | |
| 64 | + | |
| 65 | + | |
64 | 66 | | |
65 | 67 | | |
66 | 68 | | |
| |||
Whitespace-only changes.
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | 3 | | |
4 | | - | |
| 4 | + | |
5 | 5 | | |
6 | 6 | | |
| 7 | + | |
7 | 8 | | |
| 9 | + | |
8 | 10 | | |
9 | 11 | | |
10 | 12 | | |
11 | 13 | | |
| 14 | + | |
| 15 | + | |
12 | 16 | | |
13 | 17 | | |
14 | 18 | | |
| |||
18 | 22 | | |
19 | 23 | | |
20 | 24 | | |
| 25 | + | |
21 | 26 | | |
22 | 27 | | |
23 | 28 | | |
24 | 29 | | |
| 30 | + | |
25 | 31 | | |
26 | 32 | | |
27 | 33 | | |
| |||
36 | 42 | | |
37 | 43 | | |
38 | 44 | | |
| 45 | + | |
| 46 | + | |
| 47 | + | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
| 53 | + | |
| 54 | + | |
39 | 55 | | |
40 | 56 | | |
41 | 57 | | |
| |||
0 commit comments