Project

Profile

Help

Story #3972

Story #3968: As a Pulp user, I can protect content I have stored in Pulp

As a plugin writer, I can define a type of ContentGuard

Added by daviddavis about 1 year ago. Updated 3 months ago.

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

100%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Documentation
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Sprint 56

Description

This is probably mostly a docs story.

A couple notes:

- Examples might include cert-based auth, header auth, etc
- ContentGuard types can be shipped independently of content plugins

Also, ContentGuard should be available in the plugin API.


Related issues

Blocked by Pulp - Story #4074: As a user, the content guard logic needs to be loaded and used by the content app. MODIFIED Actions

Associated revisions

Revision 0c8c49f8 View on GitHub
Added by bmbouter 3 months ago

Adds ``ContentGuard`` plugin writer docs

The ``ContentGuard`` was usable in the plugin API before, but there were
not very good docs on it. This explains to plugin writers how to define
and use detail ``ContentGuard`` objects.

https://pulp.plan.io/issues/3972
closes #3972

History

#1 Updated by jortel@redhat.com about 1 year ago

  • Related to Story #3969: As a user, I can CRUD a ContentGuard added

#2 Updated by jortel@redhat.com about 1 year ago

  • Related to deleted (Story #3969: As a user, I can CRUD a ContentGuard)

#3 Updated by jortel@redhat.com about 1 year ago

  • Blocked by Story #3969: As a user, I can CRUD a ContentGuard added

#4 Updated by jortel@redhat.com about 1 year ago

This may also include importing ContentGuard into the plugin API (plugin/__init__.py).

#5 Updated by daviddavis about 1 year ago

  • Description updated (diff)

#6 Updated by jortel@redhat.com about 1 year ago

  • Groomed changed from No to Yes
  • Sprint Candidate changed from No to Yes

#7 Updated by amacdona@redhat.com about 1 year ago

  • Sprint set to Sprint 43

#8 Updated by rchan about 1 year ago

  • Sprint changed from Sprint 43 to Sprint 44

#9 Updated by jortel@redhat.com about 1 year ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to jortel@redhat.com

#10 Updated by jortel@redhat.com about 1 year ago

  • Blocked by deleted (Story #3969: As a user, I can CRUD a ContentGuard)

#11 Updated by jortel@redhat.com about 1 year ago

  • Blocked by Story #4074: As a user, the content guard logic needs to be loaded and used by the content app. added

#12 Updated by rchan 12 months ago

  • Sprint changed from Sprint 44 to Sprint 45

#13 Updated by rchan 11 months ago

  • Sprint changed from Sprint 45 to Sprint 46

#14 Updated by rchan 10 months ago

  • Sprint changed from Sprint 46 to Sprint 47

#15 Updated by rchan 9 months ago

  • Sprint changed from Sprint 47 to Sprint 48

#16 Updated by rchan 8 months ago

  • Sprint changed from Sprint 48 to Sprint 49

#17 Updated by dkliban@redhat.com 8 months ago

  • Status changed from ASSIGNED to NEW
  • Assignee deleted (jortel@redhat.com)
  • Tags Documentation added

#18 Updated by rchan 8 months ago

  • Sprint changed from Sprint 49 to Sprint 50

#19 Updated by rchan 7 months ago

  • Sprint changed from Sprint 50 to Sprint 51

#20 Updated by rchan 6 months ago

  • Sprint changed from Sprint 51 to Sprint 52

#21 Updated by amacdona@redhat.com 6 months ago

  • Sprint/Milestone set to 3.0

#22 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

#23 Updated by bmbouter 5 months ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to bmbouter

#24 Updated by rchan 5 months ago

  • Sprint changed from Sprint 52 to Sprint 53

#25 Updated by amacdona@redhat.com 5 months ago

  • Sprint changed from Sprint 53 to Sprint 54

#26 Updated by ttereshc 4 months ago

  • Sprint changed from Sprint 54 to Sprint 55

#27 Updated by dkliban@redhat.com 3 months ago

  • Sprint changed from Sprint 55 to Sprint 56

#28 Updated by bmbouter 3 months ago

  • Status changed from ASSIGNED to POST

#29 Updated by bmbouter 3 months ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

Please register to edit this issue

Also available in: Atom PDF