Project

Profile

Help

Task #2373

closed

Planning on how to support global importer settings

Added by jortel@redhat.com over 7 years ago. Updated almost 5 years ago.

Status:
CLOSED - COMPLETE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Sprint:
Quarter:

Description

Planning on how to support global importer settings in pulp3 based on this pulp2 story https://pulp.plan.io/issues/1251.

Things to consider:

  • Are global settings used for importer creation only (Like a template)?
  • If not for creation only - what is expected behavior when the global setting changes? Applied to all existing importers?
  • Which settings can be global (just credentials, proxy etc)? Limited to just standard settings to also custom settings (fields) added by plugin importer models?
  • Are globals stored in the DB?
  • How are globals associated (applied) to specific importers? Statically? Dynamically (part of sync call)?
  • Could this be address with mass update instead? For example: update proxy_url on all/filtered set of importers?

Related issues

Related to Pulp - Story #3108: As a user, I can manage Download Profiles and associate them with ImportersCLOSED - WONTFIX

Actions

Also available in: Atom PDF