Task #4633: Define Collection model - Ansible Plugin - Pulp

Actions

Send by e-mail Copy link

Task #4633

closed

Define Collection model

Added by bmbouter about 5 years ago. Updated over 3 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

bmbouter

Sprint/Milestone:

0.1 Release

Start date:

Due date:

% Done:

100%

Estimated time:

Platform Release:

Groomed:

Yes

Sprint Candidate:

Tags:

Sprint:

Sprint 51

Quarter:

Description

Define 1 model type, Collection that inherits from Content. It will store 4 string values and a single artifact.

namespace: "acme"
name: “jenkins”
version: "3.5.0"
min_ansible_version: “2.4”

Related issues

Actions

Copy link

Updated by bmbouter about 5 years ago

Subject changed from define Collection model and CollectionVersion content model to Define Collection model and CollectionVersion content model

Actions

Copy link

Updated by bmbouter about 5 years ago

Description updated (diff)

@daviddavis why did we go with the Role, RoleVersion design versus just a RoleVersion and then fancy views to deduplicate the Role data?

Actions

Copy link

Updated by daviddavis about 5 years ago

Two reasons. The first was normalization. The second is that we were basing our models off the ones in Galaxy which also had a Role[0] and a RoleVersion[1].

I'm not opposed to having one model especially since it seems like Collection is a lot smaller than Role was.

[0] https://github.com/ansible/galaxy/blob/c5916e5853a7022a38df1465abc442e29cb96a08/galaxy/main/models.py#L238
[1] https://github.com/ansible/galaxy/blob/c5916e5853a7022a38df1465abc442e29cb96a08/galaxy/main/models.py#L551

Actions

Copy link