Repository navigation
Add populate_tenant_history management command - #347
Merged
Merged
Conversation
kiwitcms-bot
force-pushed
the
populate-tenant-history
branch
from
October 4, 2026 18:08
538d17e to
34cb699
Compare
kiwitcms-bot
force-pushed
the
populate-tenant-history
branch
from
October 4, 2026 18:14
34cb699 to
4263112
Compare
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
2 participants
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.
This is the multi-tenant version of
simple_history'spopulate_historymanagement command, plus wiring it intoupgrade_tenants.populate_tenant_historyinherits from the upstreamsimple_history.management.commands.populate_history.Commandand only adds the multi-tenant bits:handle()loops over all tenants and calls the inheritedhandle()insidetenant_context()for each one, printing the same per-tenant start/end banners (with timestamp) that the other tenant commands use.add_arguments()adds a--dry-runoption._bulk_history_create()returns early when--dry-runis given, otherwise it delegates to the upstream implementation. All other behaviour (models/--auto/--batchsize, existing-history detection, batching) is reused from upstream.upgrade_tenantsnow runspopulate_tenant_history --autoas its first step, beforerefresh_tenant_permissions(the remaining steps are renumbered accordingly).Includes tests exercising the multi-tenant population and the
--dry-runmode.