Skip to content

[PULP-1956] Fix TaskSchedule dispatching in wrong domain#7822

Draft
jobselko wants to merge 1 commit into
pulp:mainfrom
jobselko:ts_domain
Draft

[PULP-1956] Fix TaskSchedule dispatching in wrong domain#7822
jobselko wants to merge 1 commit into
pulp:mainfrom
jobselko:ts_domain

Conversation

@jobselko

Copy link
Copy Markdown
Member

📜 Checklist

  • Commits are cleanly separated with meaningful messages (simple features and bug fixes should be squashed to one commit)
  • A changelog entry or entries has been added for any significant changes
  • Follows the Pulp policy on AI Usage
  • (For new features) - User documentation and test coverage has been added

See: Pull Request Walkthrough

@jobselko jobselko self-assigned this Jun 29, 2026
@jobselko jobselko force-pushed the ts_domain branch 2 times, most recently from 54214cc to ad5ae66 Compare June 29, 2026 19:00
Assisted By: Claude Opus 4.6
Comment on lines +282 to +286
pulp_domain = RelatedField(
help_text=_("Domain this schedule belongs to."),
read_only=True,
view_name="domains-detail",
)

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.

One thing to note is that once you add a pulp_domain relationship to a model it will then be scoped to that domain and thus having a read-only field on the serializer is redundant (the domain is always present in the objects href). The other way we've added a domain relation without the object becoming a part of the domain is by naming the field domain like we did for UserRole and GroupRole.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Ohhh, if anything this is not a bugfix afaics. Scheduled tasks have a very limited scope to global housework duties.
So what really is the ask? Making the task schedule itself a domain scoped object?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants